Skip to content

Fix auto-update of galexie versions - #961

Merged
leighmcculloch merged 4 commits into
mainfrom
galexie-v27-release-workflow-va0r6v
Jul 31, 2026
Merged

Fix auto-update of galexie versions#961
leighmcculloch merged 4 commits into
mainfrom
galexie-v27-release-workflow-va0r6v

Conversation

@leighmcculloch

@leighmcculloch leighmcculloch commented Jul 29, 2026

Copy link
Copy Markdown
Member

What

Recognise a dependency ref as a version when it carries a repo-specific tag prefix, and compare it against the latest release sharing that prefix.

Why

galexie tags releases as galexie-vX.Y.Z, so the leading-v check skipped it on every Auto Update run and it never moved past galexie-v26.1.0.

Close #959

cc @stellar/platform-eng

@github-project-automation github-project-automation Bot moved this to Backlog (Not Ready) in DevX Jul 29, 2026
@leighmcculloch
leighmcculloch requested a review from a team July 29, 2026 14:18
@leighmcculloch
leighmcculloch marked this pull request as ready for review July 29, 2026 14:18
Copilot AI review requested due to automatic review settings July 29, 2026 14:18
@leighmcculloch
leighmcculloch enabled auto-merge (squash) July 29, 2026 14:18
@leighmcculloch leighmcculloch changed the title Match prefixed release tags in auto-update Fix auto-update of galexie versions Jul 29, 2026
@leighmcculloch
leighmcculloch requested a review from a team July 29, 2026 14:19

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates auto-update logic to support repository-prefixed release tags such as Galexie’s.

Changes:

  • Recognizes prefixed semantic-version refs.
  • Filters releases using the detected prefix.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .scripts/auto-update Outdated
@fnando

fnando commented Jul 30, 2026

Copy link
Copy Markdown
Member

there are some failing jobs.

leighmcculloch pushed a commit that referenced this pull request Jul 30, 2026
The `future` image still pinned protocol 26 releases, so it can't join
futurenet (now on protocol 28) and its rpc v26 pin no longer compiles on
stable Rust. This pins core, rpc, and horizon to the commits futurenet
reports running, and xdr to the CAP-0083/CAP-0085 ungate commit since no
release has it yet.

galexie moves to its latest release and lab to `main` — neither has
protocol 28 support to track. `nightly-next`'s default protocol goes to
28 to match futurenet.

Fixes #960, unblocks #961.
@leighmcculloch

Copy link
Copy Markdown
Member Author

there are some failing jobs.

Fixed by:

@fnando fnando left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@leighmcculloch
leighmcculloch merged commit 73e457d into main Jul 31, 2026
102 checks passed
@leighmcculloch
leighmcculloch deleted the galexie-v27-release-workflow-va0r6v branch July 31, 2026 11:57
@github-project-automation github-project-automation Bot moved this from Backlog (Not Ready) to Done in DevX Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Auto Update never bumps galexie because its release tags are prefixed

3 participants