Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

UI still showing "next" as version when using "v1.0" tag #2225

Closed
5 tasks done
philipkozeny opened this issue Aug 16, 2023 · 4 comments · Fixed by #2227
Closed
5 tasks done

UI still showing "next" as version when using "v1.0" tag #2225

philipkozeny opened this issue Aug 16, 2023 · 4 comments · Fixed by #2227
Labels
bug Something isn't working build CI pipeline related
Milestone
1.0.3

Comments

@philipkozeny
Copy link

Component

web-ui

Describe the bug

Just a small UI issue, but running the v1.0 tag instead of latest, v1.0.2 is showing next as the version in the UI and via /version.

System Info

v1.0: {"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-d9e06696"}
latest: {"source":"https://github.com/woodpecker-ci/woodpecker","version":"1.0.2"}

Additional context

No response

Validations

  • Read the Contributing Guidelines.
  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
  • Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.
@philipkozeny philipkozeny added the bug Something isn't working label Aug 16, 2023
@6543
Copy link
Member

6543 commented Aug 16, 2023 •
edited
Loading

I think this was already reported somewhere 👀 cant find it

@6543 6543 added the build CI pipeline related label Aug 16, 2023
@6543
Copy link
Member

6543 commented Aug 16, 2023

It's an issue with our build pipeline ...

@philipkozeny
Copy link
Author

I think this was already reported somewhere 👀 cant find it

Yeah, I was the one who asked if I should open an issue on discord when testing that :)

@6543 6543 added this to the 1.0.3 milestone Aug 16, 2023
@6543 6543 mentioned this issue Aug 16, 2023
Merged
@6543
Copy link
Member

6543 commented Aug 16, 2023

-> #2227

6543 added a commit that referenced this issue Aug 16, 2023
@6543
Set correct version for release branch releases (#2227)
8d19d3b 
close  #2225

also make the sha 10 chars long instead of 8, to match the docker tags
6543 added a commit to 6543-forks/woodpecker that referenced this issue Aug 16, 2023
@6543
Set correct version for release branch releases (woodpecker-ci#2227)
d56b86f 
close  woodpecker-ci#2225

also make the sha 10 chars long instead of 8, to match the docker tags
@6543 6543 mentioned this issue Aug 16, 2023
Merged
lafriks pushed a commit that referenced this issue Aug 16, 2023
@6543
Set correct version for release branch releases (#2227) (#2229)
24910b6 
Backport  #2227

close  #2225

also make the sha 10 chars long instead of 8, to match the docker tags
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working build CI pipeline related
Projects
None yet
Milestone
1.0.3
Development

Successfully merging a pull request may close this issue.

Set correct version for release branch releases 6543-forks/woodpecker
2 participants
@philipkozeny @6543