Skip to content
This repository has been archived by the owner on May 30, 2022. It is now read-only.

GitHub Actions release tags don't match actual releases #126

Open
antichris opened this issue Mar 14, 2022 · 0 comments
Open

GitHub Actions release tags don't match actual releases #126

antichris opened this issue Mar 14, 2022 · 0 comments

Comments

@antichris
Copy link

antichris commented Mar 14, 2022 •
edited
Loading

Starting at 6.12.1, all the v6.x releases made by GitHub Actions point to tags without a v prefix, that don't match up the v-prefixed ones. There are substantial differences betweenv/non-v tags in each pair.

For a recent example: there is a tag v6.14.5 (notice the v prefix) and a release v6.14.5, but the release is actually attached to the tag 6.14.5 (without a v prefix). The tags v6.14.5 and 6.14.5 each point to different commits.

6.14.5, 6.14.2 and (at the time of writing) master all point to the same commit. Also, 6.12.5, 6.13.0 and v7.0.0-beta.21 all point to the same commit, while v6.12.5 and v6.13.0 each point to a different one.
@antichris antichris changed the title Fix GitHub Actions release tags GitHub Actions release tags don't match actual releases Mar 16, 2022
antichris added a commit to antichris/ledobe that referenced this issue Mar 16, 2022
@antichris
Makefile: use v-prefixed version tags of core lib Node bindings
71b0f3f 
`6.14.5` and `v6.14.5` in their repository each point to a different
commit, the latter being a more recent one. `6.14.5` along with `6.14.2`
appear to be stuck at the tip of their `master` that they  don't seem
to update anymore.

Caused by LedgerHQ/lib-ledger-core-node-bindings#126
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@antichris