Integrate changesets #25
Merged
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
aacevedoosorio
approved these changes
Oct 31, 2024
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.
To smooth the versioning process and put less coginitive load on developers. The way it works is that every PR might include a changeset (or a few of them) that would describe WHAT has been done and HOW it affects a package (there is only one ATM and it is likely to keep it that way). The
WHATpart later becomes a part of apkg/{PACKAGE_NAME}/CHANGELOG.mdand theHOWpart determines the version bump. Read the addedREADME.mdfile for more details.In the future it will be possible to automate the versioning and releasing. But having that process in place for manual execution is already benefitial.