Skip to content

Conversation

@7heMech
Copy link
Contributor

@7heMech 7heMech commented Jan 17, 2025

This is probably the last version before 1.2, idk how the migration works on replit then.

  • This is fully backward and forward compatible

@7heMech 7heMech requested a review from a team as a code owner January 17, 2025 11:40
@7heMech 7heMech requested review from cbrewster and removed request for a team January 17, 2025 11:40
Copy link
Contributor

@blast-hardcheese blast-hardcheese left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! Thank you!

@blast-hardcheese blast-hardcheese merged commit 60d117c into replit:main Jan 22, 2025
3 checks passed
@blast-hardcheese
Copy link
Contributor

To answer your question, when 1.2 gets released, we add an entry with the last HEAD from this repo that had the old version into pkgs/historical-modules/default.nix (see 71f34ae), then just bump the version to 1.2 as normal.

This persists the last known release of a historical module, but still permits this repository to describe the whole ecosystem of all supported modules, as well as allows us to do hotfixes if some major vulnerability that absolutely must be patched is discovered.

@7heMech
Copy link
Contributor Author

7heMech commented Feb 4, 2025

Thanks! So I can make a PR like, the ones I've been doing till now, and it'd be all fine?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants