DAT-15071 automatically bump version via the release workflow #388
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
…to improve security
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
…OT in pom.xml refactor: split extension-update-version.yml into extension-release-prepare.yml, extension-release-perform.yml, and extension-release-rollback.yml to improve readability and maintainability of create-release.yml workflow
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
…21.1-SNAPSHOT to fix compatibility issues with other dependencies refactor: remove integration-tests job from create-release.yml workflow as it is no longer needed after the downgrade of liquibase-mongodb version in pom.xml
… in draft-release and release-perform jobs since it is not necessary for these jobs to run successfully.
…HOT to 4.21.1-SNAPSHOT to fix compatibility issues with other dependencies
… to 4.21.1-SNAPSHOT for compatibility reasons
…reation step to target/liquibase-mongodb-*.jar
chore(release-published.yml): update file path for jar file in Maven deploy step to target/${{ github.event.release.tag_name}}.jar
chore(pom.xml): update version to 4.21.1-SNAPSHOT for Liquibase MongoDB Extension
…x deployment issue The Maven Central Repository URL was updated to fix the deployment issue. The previous URL was causing the deployment to fail.
… to 4.21.1-SNAPSHOT for compatibility reasons
… generated by release-prepare step fix(release-published.yml): fix file path for target jar in Publish to the Maven Central Repository step chore(pom.xml): update liquibase-mongodb version to 4.21.1-SNAPSHOT
…kflow fix(pom.xml): update liquibase-mongodb version from 4.23.1-SNAPSHOT to 4.21.1-SNAPSHOT for compatibility reasons
… Maven deploy command to specify the location of the POM file
…loy command to fix deployment to Maven Central Repository fix(pom.xml): downgrade liquibase-mongodb version from 4.23.1-SNAPSHOT to 4.21.1-SNAPSHOT to resolve compatibility issues
…t repository URL for publishing to Maven Central fix(pom.xml): update version of liquibase-mongodb to 4.21.1-SNAPSHOT fix(pom.xml): update repository URLs for release and snapshot repositories in distributionManagement section
…bucket The commit adds a new step to the release-published.yml workflow file. This step is responsible for uploading xsd files to an S3 bucket. The step first downloads the liquibase mongodb xsd repository using the actions/checkout action. Then, it sets the necessary environment variables for AWS access. Next, it uses the aws s3 sync command to sync the xsd files from the local repository to the specified S3 bucket. Finally, it performs additional operations on the index.htm file, such as adding links for all xsd files (except liquibase-mongodb-latest.xsd and index.htm), and syncs the modified index.htm file with the S3 bucket.
…ication with different versions of Java and MongoDB chore(release-published.yml): sync updated index-file to S3 bucket for MongoDB XML namespace documentation
…for draft-release and release-rollback jobs to ensure integration tests are run before creating a release or rolling back a release
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.
https://datical.atlassian.net/browse/DAT-15071