Skip to content
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

update master with changes from release branch #5192

Merged
merged 4 commits into from
Nov 14, 2023
Merged

Conversation

StevenMassaro
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

@sayaliM0412 sayaliM0412 added the skipReleaseNotes skip the Draft Release Notes label Nov 10, 2023
filipe and others added 4 commits November 13, 2023 11:19
Only calls database.commit if we did something, otherwise we are will be calling it for no reason and in cloud databases it means a lot of trouble.
@StevenMassaro StevenMassaro changed the title generate deployment ID for all update family, and mark-next-changeset-ran commands (DAT-16240) update master with changes from release Nov 13, 2023
@StevenMassaro StevenMassaro changed the title update master with changes from release update master with changes from release branch Nov 13, 2023
@filipelautert filipelautert merged commit 5f54536 into master Nov 14, 2023
34 of 35 checks passed
@filipelautert filipelautert deleted the release branch November 14, 2023 12:49
@filipelautert filipelautert restored the release branch November 14, 2023 12:49
sayaliM0412 pushed a commit that referenced this pull request Nov 14, 2023
#5206)

* update master with changes from release branch (#5192)

* generate deployment ID for all update family, and mark-next-changeset-ran commands (DAT-16240) (#5185)

* Invoke database.commit only if needed (#5182)

Only calls database.commit if we did something, otherwise we are will be calling it for no reason and in cloud databases it means a lot of trouble.

* Update changelog.txt

---------

Co-authored-by: filipe <flautert@liquibase.org>
Co-authored-by: rberezen <ruslan.berezenskyi@gmail.com>

* chore(release-published.yml): update pom.xml versions to match the current version to ensure consistency in the release artifacts

---------

Co-authored-by: Steven Massaro <steven.massaro.web@gmail.com>
Co-authored-by: filipe <flautert@liquibase.org>
Co-authored-by: rberezen <ruslan.berezenskyi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skipReleaseNotes skip the Draft Release Notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants