4.3.0

[skumagai]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[skumagai]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/code-server-feedstock/actions/runs/2237382533.

[skumagai]

Turned out there are some dangling symlinks in the 4.3.0 release for macOS. On macOS, cp -r handles symlinks different from cp -R causing the initial build error on that system.

[skumagai]

@xhochy Can you take a look and merge this if it's good enough?

[skumagai]

4.4.0 is already merged. No need to package 4.3.0.