ci: add production release automation workflows - #760
Open
ehsandeep wants to merge 6 commits into
Open
Conversation
- Replace goreleaser/goreleaser-action@v6 with projectdiscovery/actions/goreleaser@v1.29.4 - Add svu-based next-version computation (read-only, no tag push) - Set GORELEASER_CURRENT_TAG so snapshot artifacts carry the real next version - Pin permissions to contents:read so the job cannot push tags - Add .goreleaser.yml and workflow self-trigger to path filters - Write next version + artifact list to $GITHUB_STEP_SUMMARY This is a PR-only dry-run: release:true + --snapshot runs the full goreleaser pipeline (build, archive, checksums) but skips publish/announce. No tags or releases are created from PR builds. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- add release-tag workflow for automatic main tagging and manual tag controls - switch release-binary to projectdiscovery/actions/goreleaser - require explicit tags for manual publish runs and support announce toggles - restore release-test workflow to its pre-POC state so the PR stays focused Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- replace low-level manual inputs with run-mode, version-bump, and exact-version - keep automatic push-to-main tagging path unchanged - keep manual dry-run and explicit exact tag support in a simpler form - retain summary output for manual and automatic runs Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- change release-tag manual version-bump option from exact to custom - rename exact-version input to custom-version - keep behavior unchanged, only simplify naming for the workflow UI Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- remove automatic tag creation on push to main - keep manual dispatch with simplified run-mode and version-bump controls - preserve explicit tag creation as the release gate Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- run weekly (every Monday 09:00 UTC) and create a tag only if there are new commits since the last release tag - keep manual workflow_dispatch with run-mode, version-bump, custom-version - manual dry-run default so accidental triggers are safe Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
This PR adds the actual release automation flow for proxify, built on the reusable pieces already merged in
projectdiscovery/actions.Files changed
.github/workflows/release-tag.yml— new workflowmainprojectdiscovery/actions/svu-next@v1.29.4to compute and create the next release tagworkflow_dispatchcontrols for:refdry-runalways-bumpprereleasemetadatatag-prefixv0.github/workflows/release-binary.yml— production publish workflowpush.tags: v*goreleaser/goreleaser-actionusage toprojectdiscovery/actions/goreleaser@v1.29.4workflow_dispatchsupport with:tagrefannouncetogglegoreleaser-argsv*tagGORELEASER_CURRENT_TAGexplicitly for manual publish runsResulting release flow
Automatic path
mainrelease-tag.ymlcomputes the next version and pushes the tagrelease-binary.ymlrelease-binary.ymlpublishes the GitHub release and binaries via GoReleaserManual path
Guardrails kept in the real workflow
v*tagWhy this uses
projectdiscovery/actionsThe release safety and shared behavior now live centrally in the actions repo:
svu-nexthandles next-version calculation and optional dry-run tagginggoreleaserwraps the shared GoReleaser invocationThat keeps proxify as a thin consumer and makes rollout to other repos straightforward.