[NOD-530] feat: Semantic versioning, new GH Action add_patch_label, n… #6
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
|
Kudos, SonarCloud Quality Gate passed!
|
andrea-deri
deleted the
NOD-530-adeguamento-alla-nuova-gestione-semver
branch
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.
NOD-530 feat: Semantic versioning, new GH Action add_patch_label, new java version
This PR is crucial for updating the repositories on GitHub Actions to utilize the new management of semantic versioning effectively.
List of Changes
GH Action Version Update: The version of the GH Action setup for semantic versioning has been updated: nodo5-semver-setup@[SHA].
New GH Action Addition: The new GH Action add_patch_label.yml has been added.
Java Version Update for Pipeline: The new java version has been set to the 17th.
Motivation and Context
This PR aims to keep the GitHub Actions updated and to improve the semantic versioning processing.
How Has This Been Tested?
The changes have been tested by running the pipeline.
Types of changes
Checklist: