README: update for new version #7
Closed
Conversation
This file contains 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
Looks like this action runner is not using "long-running branches", which means that to use the latest version of this action runner, the usage instructions need to be updated. Alternatively, please consider having a `v1` tag which moves on every release within the `1.x` range or have a `v1` branch for the whole `1.x` development cycle. This would mean that people would automatically get the latest version and don't have to update their workflows.
jrfnl
added a commit
to Automattic/VIP-Coding-Standards
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
jrfnl
added a commit
to Automattic/VIP-Coding-Standards
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
jrfnl
added a commit
to jrfnl/PHP_CodeSniffer
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
jrfnl
added a commit
to PHPCompatibility/PHPCompatibility
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
jrfnl
added a commit
to sirbrillig/phpcs-variable-analysis
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
jrfnl
added a commit
to WordPress/WordPress-Coding-Standards
that referenced
this pull request
Oct 14, 2022
The `xmllint-problem-matcher` action runner has released a new version which updates it to use node 16. This gets rid of a warning which was shown in the action logs. Note: I've [suggested to the author to use long-running branches for the action runner instead](korelstar/xmllint-problem-matcher#7), which would make this update redundant, but no telling if or when they'll respond to that, let alone if they will follow my suggestion. Refs: * https://github.com/korelstar/xmllint-problem-matcher/releases/tag/v1.1
|
Hey @jrfnl , thanks for your remarks! To be honest: I did some mistakes when publishing the last release (
Sorry for these confusions, this was not best practice. From now on, I will create releases using the semantic versioning structure (v Could you please check if everything is fine, now? |
This was referenced Oct 23, 2022
Merged
Merged
|
@korelstar Sorry for my delayed response! I have tested with a couple of repos and can confirm all is fine now. For those repos in which I'd already switched to I will close this PR now as it is no longer needed. Thank you for your prompt action and for maintaining this project! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looks like this action runner is not using "long-running branches", which means that to use the latest version of this action runner, the usage instructions need to be updated.
Alternatively, please consider having a
v1tag which moves on every release within the1.xrange or have av1branch for the whole1.xdevelopment cycle.This would mean that people would automatically get the latest version and don't have to update their workflows.