-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAT-18309 DevOps :: Extensions are creating 2 tags #234
Conversation
… and compatibility 🔧 (create-release.yml): Update sonar-push.yml workflow to use the main branch for better maintenance 🔧 (create-release.yml): Add support for setting up JDK 17 for the workflow 🔧 (create-release.yml): Add support for setting up Maven with the specified version 🔧 (create-release.yml): Add maven-settings-xml-action to configure repositories and servers for Maven 🔧 (create-release.yml): Extract version from pom.xml and set it as an environment variable for the workflow 🔧 (create-release.yml): Update Create Release step to use the extracted version for the release draft tag
…n release prepare step to prevent automatic pushing of changes 🔧 (extension-release-prepare.yml): add git add and git commit commands to stage and commit changes made during maven release prepare step 🔧 (extension-release-published.yml): update the version of the extension-release-prepare.yml workflow to DAT-18309
…lease title and tag name in GitHub release API to match the project version.
…n v0.7.8 for sonar job 🔧 (extension-release-published.yml): change default value of deployToMavenCentral to boolean true
@@ -16,7 +16,7 @@ on: | |||
deployToMavenCentral: | |||
description: 'Specify it if you want to deploy to maven' | |||
required: false | |||
default: 'true' | |||
default: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was failing @sayaliM0412
… pom.xml file for commit to avoid adding unnecessary files
…ase preparation by deleting and force pushing the temporary tag to prevent conflicts
🔧 (.github/workflows/extension-attach-artifact-release.yml): Fix tag_name value to include 'v' prefix before version number
@@ -51,5 +51,3 @@ template: | | |||
## Changes | |||
|
|||
$CHANGES | |||
|
|||
**Full Changelog**: https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...$REPOSITORY-v$RESOLVED_VERSION |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as liquibase/liquibase so it ca be auto generated
…ension-release-prepare.yml file to use the 'main' branch instead of a specific branch.
Do we want to change all |
Sounds good for now. I ended up updating the |
https://datical.atlassian.net/browse/DAT-18309