Introduce the javy-release crate#1169
Merged
saulecabrera merged 3 commits intobytecodealliance:mainfrom Apr 6, 2026
Merged
Conversation
saulecabrera
commented
Apr 3, 2026
Member
Author
There was a problem hiding this comment.
I'll update the contributing documentation in a follow-up commit in this PR. I wanted to put this out first to gather any feedback/thoughts.
Member
Author
|
It's important to note that the functionality in this PR assumes #1167, which I think we should merge, even if we don't end up merging this PR. |
jeffcharles
approved these changes
Apr 6, 2026
Collaborator
jeffcharles
left a comment
jeffcharles
left a comment
There was a problem hiding this comment.
I'm all for more automation
saulecabrera
force-pushed
the
introduce-the-release-crate
branch
2 times, most recently
from
8cd3319 to
41d8b98
Compare
This commit introduces the `javy-release` crate. The idea behind this crate is to provide a utility to partially automate our release process, at least initially. In its current form, this crate adds the necessary functionality to toggle the release/dev versions according to our versioning system. Even though publishing to crates.io should be possible, I've opted exclude such functionality in the initial state of this crate mostly for simplicity. Said functionality can be added as a follow-up if this crate gets adopted. Furthermore, the principal motivation for this change is to ease the release process, which is currently manual and potentially error prone. I've gone through this process twice, and in every instance it's unclear to me the order of operations that I need to follow to start a successful release.
saulecabrera
force-pushed
the
introduce-the-release-crate
branch
from
41d8b98 to
4c032b4
Compare
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
2 participants
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 commit introduces the
javy-releasecrate.The idea behind this crate is to provide a utility to partially automate our release process, at least initially. In its current form, this crate adds the necessary functionality to toggle the release/dev versions according to our versioning system.
Even though publishing to crates.io should be possible, I've opted exclude such functionality in the initial state of this crate mostly for simplicity. Said functionality can be added as a follow-up if this crate gets adopted.
Furthermore, the principal motivation for this change is to ease the release process, which is currently manual and potentially error prone. I've gone through this process twice, and in every instance it's unclear to me the order of operations that I need to follow to start a successful release.