-
Notifications
You must be signed in to change notification settings - Fork 8
feat: add changelog section with separate beta/stable streams to package manifest and testing script #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@NorthernMan54 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
@copilot The change log is not accurate. The package maintains 2 streams of TAG's, based on PKG_RELEASE_TYPE. |
Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
You're absolutely right! I've fixed the changelog logic to properly separate the beta and stable tag streams. The manifest now:
This ensures that beta changelogs show changes since the last beta release, and stable changelogs show changes since the last stable release, providing accurate and relevant change information for each stream. Fixed in commit |
@copilot How can this be tested outside of the release process ? |
…utside release process Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
You can test the changelog generation outside of the release process using the new # Test stable changelog generation
./test-changelog.sh
# Test beta changelog generation
PKG_RELEASE_TYPE=beta ./test-changelog.sh
# Test with custom parameters
PKG_RELEASE_TYPE=beta PKG_RELEASE_VERSION=1.2.3-beta.1 OUTPUT_FILE=my-test.md ./test-changelog.sh The script replicates the exact changelog logic from
This is helpful for validating changelog logic changes, understanding what will be included in upcoming releases, and testing edge cases. The script is documented in the updated BUILD.md file. Fixed in commit |
@copilot Pls create a test directory and move test-change log.sh to that directory |
Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
Created test/ directory and moved test-changelog.sh there. Updated all references in BUILD.md and the script's self-referencing paths. The script works correctly from its new location at ./test/test-changelog.sh. Fixed in commit |
@copilot remove beta-example.md |
Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
Removed beta-example.md test output file. Fixed in commit |
This PR enhances the Package Manifest file to include details about what has changed with each release, addressing the need for better visibility into release contents.
Enhanced Package Manifest
The manifest file now includes a new "What's Changed" section that automatically generates a changelog based on git commit history:
Implementation Details
git log
to get commits since the last release tagtest/test-changelog.sh
script for independent testingtest/
directorybeta-example.md
Testing Capability
Added
test/test-changelog.sh
script that allows testing the changelog generation independently of the full release process:The test script replicates the exact changelog logic from
build.sh
and provides:Integration
The changelog generation is seamlessly integrated into the existing build process:
build.sh
- only adds content after the package versions tableThis enhancement provides users with immediate visibility into what has changed in each release without requiring them to navigate to GitHub or external documentation. The separate stream handling ensures that beta changelogs show changes since the last beta release, and stable changelogs show changes since the last stable release.
Fixes #158.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.