Version Packages #309
Merged
Version Packages #309
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
728bbed
to
0664665
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@empirica/core@1.3.3
Patch Changes
fef4bb4: Empirica proxy download was using hard links and it could break upgrades. It now uses copy for safety.
That does mean we are using up more space on disk, but it remain relatively minimal all things
considered. We might want to look into pruning old versions at some point, but it does not seem
critical at the moment since empirica binaries are not that large.
We've also improved looking up the current project release version by looking for the .empirica
directory in parent directories. This is helpful in the case of export, which runs in subdirectory and
will not pick up the correct empirica version.
681c4c6:
empirica upgradewill automaticall run in "global" mode when not in a project.