Add GHA workflow to publish releases; stale file cleanup#290
Merged
Conversation
Add a GitHub Actions release workflow: push a semver tag, or run it with `-f version=vX.Y.Z` to validate the version, create and push the tag, and publish the release from CI. Both paths generate the changelog with `gh release create --generate-notes`, so the manual step is gone. The repo has been a single Go module (github.com/rstudio/platform-lib/v4) since v4, so remove the tooling and docs that assumed per-module go.mod files and per-module tags: - Delete the chart/tags scripts (latest-tags.sh, generate-chart-data.sh, generate-chart.sh), their justfile targets, and the .chart ignore/clean entries. The chart graphed dependencies between modules that no longer exist under a single module. - Rewrite the top-level release and testing sections and the pkg READMEs for the single module, and fix test examples that pointed at packages and import paths that no longer exist.
glin
changed the title
jonyoder
approved these changes
Jul 20, 2026
jonyoder
left a comment
jonyoder
left a comment
Collaborator
There was a problem hiding this comment.
Great to see this added!
CDRayn
approved these changes
Jul 20, 2026
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
3 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.
Currently, platform-lib releases are done by manual tagging + creating a GH release. This adds a GHA workflow to automatically tag + release given a version.
Also cleans up some old release files that are no longer used.
Release workflow
.github/workflows/release.ymlpublishes a GitHub Release with a generated changelog, two ways:gh workflow run release.yml -f version=v4.3.1(validates the version, refuses duplicates, requiresmain, then tags and releases from CI, no local git)git tag v4.3.1 && git push origin v4.3.1Cleanup
The repo has been one module (
github.com/rstudio/platform-lib/v4) since v4, so:latest-tags.sh,generate-chart-data.sh,generate-chart.sh), their justfile targets, and the.chartentries.pkgREADMEs; fixed test examples pointing at packages and import paths that no longer exist.Testing
Hard to test but after merge, I'll try publishing a release, then delete the release/tag (unless we have legit changes to include, possibly some dependency bumps)