fix: switch back to package.json as it's necessary for GH actions#101
Merged
fix: switch back to package.json as it's necessary for GH actions#101
Conversation
Contributor
|
Ah, did not realize |
Member
Author
|
It's no problem. Neither did I 😄 |
Member
Author
|
@crowlKats actually, I kind of feel like it's not necessary. Isn't the version just based on the tag? |
Member
|
@dsherret so it isnt just about version, but also author & description. but i looked into it, and noticed that these are actually defined via an |
crowlKats
pushed a commit
that referenced
this pull request
May 15, 2025
(cherry picked from commit ee64dd3)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#95 used a deno.json, but we need a package.json for managing the version and publishing the action.