fix: support slashes in tags #62

Merged
earl-warren merged 5 commits from Crown0815/forgejo-release:main into main 2025-07-25 06:50:17 +00:00
Contributor
Resolves actions/forgejo-release#22
Crown0815 force-pushed main from 3efdd91f20
Some checks failed
/ integration (pull_request) Failing after 7m44s
to 9f0a9ecbf9
Some checks failed
/ integration (pull_request) Failing after 7m49s
2025-07-24 13:25:38 +00:00
Compare
Crown0815 force-pushed main from c1c15e1a16
Some checks failed
/ integration (pull_request) Failing after 7m43s
to 1faf3804c2
Some checks failed
/ integration (pull_request) Failing after 7m42s
2025-07-24 16:33:18 +00:00
Compare
Owner
https://code.forgejo.org/actions/forgejo-release/actions/runs/614#jobstep-4-500 seem relevant?
Author
Contributor

@earl-warren, do you have any idea what is causing the failure. Because already the reproduction of the issue seems to fail with the v2.0 test, but I did not touch that test.
Is there any interplay between the different integration tests?

@earl-warren, do you have any idea what is causing the failure. Because already the [reproduction of the issue](https://code.forgejo.org/actions/forgejo-release/pulls/62/commits/241daff42e82751e2205b5281e2f5b8fef560a5a) seems to fail with the `v2.0` test, but I did not touch that test. Is there any interplay between the different integration tests?
Crown0815 force-pushed main from 1faf3804c2
Some checks failed
/ integration (pull_request) Failing after 7m42s
to 84799b7d57
All checks were successful
/ integration (pull_request) Successful in 14m26s
2025-07-25 05:57:04 +00:00
Compare
Crown0815 force-pushed main from 84799b7d57
All checks were successful
/ integration (pull_request) Successful in 14m26s
to 0553b25c00
All checks were successful
/ integration (pull_request) Successful in 14m24s
2025-07-25 06:11:16 +00:00
Compare
Owner

I see you figured it out. Congrats: it is not trivial.

I see you figured it out. Congrats: it is not trivial.
earl-warren changed title from Fix #22 to fix: support slashes in tags 2025-07-25 06:46:26 +00:00
Author
Contributor

@earl-warren, I hope I did it correctly. For some reason the order was critical, though I still do not fully understand why.

@earl-warren, I hope I did it correctly. For some reason the order was critical, though I still do not fully understand why.
Author
Contributor

@earl-warren, the build on main failed. Let me know if there is anything I can do

@earl-warren, the build on main failed. Let me know if there is anything I can do
Owner

Not your fault, #64 will fix it.

Not your fault, https://code.forgejo.org/actions/forgejo-release/pulls/64 will fix it.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
actions/forgejo-release!62
No description provided.