Replies: 1 comment
-
The issue was simply due to a misconfiguration in my workflow. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm a new package developer. Here's the situation I encountered:
I made changes to my package link-generator and pushed them. Without realizing there was an error in my workflow, I incremented the package version in deno.json. GitHub Actions stopped the package update, but it seems the new version was still queued. Unaware of this, I fixed the code and pushed it again, causing the publishing process to enter an infinite loop. Is there a way to resolve this?
Incident history:
I tried changing the version to see if that would work around the issue, but that didn't seem to work.
Link-generator on Github
Link-generator on JSR
Beta Was this translation helpful? Give feedback.
All reactions