ci: make the Octopus publish idempotent - #231
Open
NickJosevski wants to merge 1 commit into
Open
Conversation
NickJosevski
force-pushed
the
chore/idempotent-octopus-publish
branch
from
August 18, 2026 05:31
9c4164d to
bf78d0c
Compare
NickJosevski
marked this pull request as ready for review
August 19, 2026 02:16
Both publish actions default to FailIfExists, so re-publishing a version that already exists fails the job. GitVersion derives a PR version from the commit count, so amending a commit or re-running a workflow reuses the version and the build information push then 409s. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
NickJosevski
force-pushed
the
chore/idempotent-octopus-publish
branch
from
August 20, 2026 05:32
bf78d0c to
a816bdc
Compare
NickJosevski
enabled auto-merge (rebase)
August 20, 2026 05:32
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.
Publish to Octopusfails whenever a version is published twice:GitVersion derives the PR version from the commit count (e.g.
6.6.1-PullRequest0229.4), so amending a commit or re-running the workflow produces the same version as the previous run, and both publish actions default toFailIfExists. Hit on #229 after a force push.Sets
overwrite_mode: OverwriteExistingon the build-information and package pushes, so a re-publish replaces the previous artefacts rather than failing.OverwriteExistingrather thanIgnoreIfExistsbecause the re-published build genuinely differs — keeping the stale package and build information would be worse than replacing them.