docs: fill in CHANGELOG entry for 0.1.1#14
Merged
Merged
Conversation
Document the fixes, additions, and changes shipped between the 0.1.0 and 0.1.1 release cuts. The 0.1.1 section was previously empty.
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
1 participant
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.
Summary
The
[0.1.1]section inCHANGELOG.mdwas empty after the release cut. This populates it from the 11 commits between the0.1.0and0.1.1tags.jira-agentmarkdown link regex (fix(python): eliminate ReDoS in jira-agent markdown link regex #10).scripts/bump-version.py, TestPyPI dry-run workflow, per-example READMEs, mypy + built-wheel smoke test in CI, real-NATS round-trip tests, alpha banner/badges in README.nats-serverto v2.14.0.Test plan
CHANGELOG.mdon GitHub and confirm the 0.1.1 section reads cleanly.