Repository navigation
Migrate to Spago and update CI - #44
Merged
Merged
Conversation
thomashoneyman
commented
Nov 4, 2026
| package: | ||
| name: dotenv | ||
| publish: | ||
| version: 4.0.4 |
Contributor
Author
There was a problem hiding this comment.
With spago.yaml, the release version needs to be specified in the manifest. I’ve proposed a patch version here, so after merging you can tag this commit as v4.0.4. Of course you can also change it if you want to release as a different version!
This file contains hidden or 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
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.
Support for
bower.jsonand other legacy or unofficial registry formats ended on August 1, 2026. This PR migrates this library to the Registry-supported Spago format. It’s the same update the registry team rolled out across the core, contrib, web, node, halogen, and other organizations. At some point in the near future, the registry will stop publishing libraries that aren’t using a supported format and this package will be dropped from e.g. the package sets.I’ve left the library code and published production dependency ranges unchanged. Alongside the manifest and related tooling updates, I’ve made the test compatibility fixes needed for the updated toolchain and dependencies. Accordingly, I suggest this only needs a patch release, as we did in the core libraries, unless you have other unreleased changes.
To complete the migration, you’d need to merge and then tag a new release, at which point the registry can pick up your library using the supported manifest. Thanks!