Skip to content

fix: set branch prefixes main:5/develop:4 and use Major.Minor.50000.0 as local fallback#78

Open
TomProkop wants to merge 2 commits into
masterfrom
users/tomas.prokop/fix-versioning-local-fallback
Open

fix: set branch prefixes main:5/develop:4 and use Major.Minor.50000.0 as local fallback#78
TomProkop wants to merge 2 commits into
masterfrom
users/tomas.prokop/fix-versioning-local-fallback

Conversation

@TomProkop

@TomProkop TomProkop commented Jun 23, 2026

Copy link
Copy Markdown
Member

Adopts the priority ordering from #77 (production outranks develop).

Changes

Branch prefix ordering

Branch Prefix Notes
develop 4 CI integration
main / master 5 Production — always wins

Fallback stays 0.0.20000.0

The 0.0 Major.Minor is intentional:

  • Clearly marks the artifact as a local/untracked build — not a CI build
  • The environment's version guard (no importing lower versions) will always reject it if any real CI artifact is already installed
  • Local builds must never reach production; this design enforces that at the version level

Supersedes #77

TomProkop and others added 2 commits June 23, 2026 16:38
… as local fallback

Adopts the priority ordering from #77 (production outranks develop) and fixes
the companion problem where local/untracked builds (fallback) could not be
deployed to a personal devbox already hydrated with develop CI artifacts.

The fallback build number 50000 is chosen because:
  - develop:4 max ever (prefix 4 + Dec 2099) = 49912  <  50000
  - main:5   min ever (prefix 5 + any Jan)   = 50001  >  50000

So a local build always beats a develop artifact, but a main CI build
always beats the local fallback — no deployment deadlocks in either direction.

The fallback also now correctly uses the project's Major.Minor instead of
the hardcoded 0.0 prefix, which caused spurious downgrades for any project
with Version >= 1.0.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…roduction

The 0.0 Major.Minor is intentional: it marks a build as local/untracked and
ensures the environment's version guard will always reject it if any real CI
artifact is already installed. Local builds should not produce legit-looking
CI version numbers.

The branch prefix ordering from the previous commit is unchanged:
  develop:4  main:5 (master:5)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant