Add automatic release workflow#32
Open
nikstuckenbrock wants to merge 1 commit into
Open
Conversation
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
2 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.
Hi all,
I noticed a rather odd behavior when using the extension. I’ve split my model into several .splib files, and in the current released version on both marketplaces (Open VSX Registry and Visual Studio Code Marketplace), all .splib files are underlined in red, indicating an issue with the Tree-sitter grammar.
After investigating, I compiled the extension locally and the issue disappeared. I spent quite some time debugging and comparing dependencies between the released and self-compiled builds, and it turns out that the latest GitHub releases (2.1.0) don’t correspond to a specific version in the marketplace (the latest one is 1.2.0). In other words, the current version on GitHub no longer has this problem.
To prevent version mismatches like this in the future, I’d like to propose introducing an automated release workflow for new tags in this repository.
For this workflow, the following repository secrets will need to be added:
OPEN_VSX_TOKENVS_MARKETPLACE_TOKENTL;DR: The version in the marketplaces differs from the version mentioned in the current GitHub release. An automated release workflow would prevent this.
Let me know what you think!
Best regards,
Nik