-
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 16350 #133
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
…er to use a noreply email address for better identification chore(extension-release-published.yml): update version of extension-release-prepare.yml used in maven-release job to DAT-16350 branch
…ck.yml version to DAT-16350 to fix rollback job failure
…ction to allow access to private repositories fix(extension-release-prepare.yml): add pushChanges=false parameter to release:prepare command to prevent accidental pushing of changes fix(extension-release-prepare.yml): add push changes step to push changes made during release preparation
… prevent token leakage
…Hub Actions workflow to fetch the complete commit history for the main branch
…to v0.8.0 to ensure compatibility with the latest version chore(extension-release-prepare.yml): set branch to main in the github-push-action step to push changes to the main branch
…' to '${{ github.head_ref }}' to dynamically use the current branch name fix(extension-release-prepare.yml): add the 'repository' parameter to the 'checkout' action to ensure the correct repository is used feat(extension-release-prepare.yml): add the 'force' and 'tags' parameters to the 'push' action to force push and push tags
…ronment variable fix(extension-release-prepare.yml): update GITHUB_TOKEN reference to use secrets.BOT_TOKEN for security reasons
…configuration to use local scope for better isolation
…rom the push step to prevent accidental force push
…ation for user name and email chore(extension-release-prepare.yml): remove unused push changes step
…ead_ref to "main" to ensure consistent behavior
… the checkout action The `persist-credentials` and `fetch-depth` options were removed from the checkout action as they were not needed.
…riable to the prepare-release job to enable authentication for GitHub API requests
…rsion to v0.5.7 in release-rollback job chore(extension-release-published.yml): update liquibase/build-logic version to v0.5.7 in maven-release job
…Hub noreply email address for better identification fix(extension-release-rollback.yml): update GitHub token reference to use secrets.BOT_TOKEN for security reasons
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.
No description provided.