Skip to content

Conversation

@dandowlinghmlr
Copy link
Contributor

@dandowlinghmlr dandowlinghmlr commented May 28, 2025

Since v3.20.0, cadence web version strings include a v

What kind of change does this PR introduce (Bug fix, feature, docs update, ...)?
Bug Fix

What is the current behavior?
Attempting to pull "docker.io/ubercadence/web:3.35.6" fails

What is the new behavior (if this is a feature change)?
Image pulls correctly with the v

Does this PR introduce a breaking change? If so, what actions will users need to take in order to regain compatibility?
non breaking

Checklists

All submissions

  • Have you followed the guidelines in our Contributing document?
  • Is this PR targeting the develop branch, and the branch rebased with commits squashed if needed?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New feature and bug fix submissions

  • Has your submission been tested locally?
  • Has documentation such as the README been updated if necessary?
  • Have you linted your new code (using rubocop and markdownlint), and are not introducing any new offenses?

sichapman and others added 2 commits May 28, 2025 08:52
@AShaww
Copy link

AShaww commented May 28, 2025

Good spot!

@sichapman sichapman merged commit bae55ed into LandRegistry:develop May 28, 2025
2 checks passed
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.

3 participants