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.

Sign up for GitHub

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

Jump to bottom

Update dependency org.liquibase:liquibase-maven-plugin to v4.29.2 #94

Merged
merged 1 commit into from
Sep 29, 2024
Merged

Update dependency org.liquibase:liquibase-maven-plugin to v4.29.2 #94

merged 1 commit into from
Sep 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 31, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.liquibase:liquibase-maven-plugin (source) 4.29.0 -> 4.29.2 age adoption passing confidence

Release Notes

liquibase/liquibase (org.liquibase:liquibase-maven-plugin)

v4.29.2: Liquibase v4.29.2

Compare Source

Liquibase 4.29.2 is a patch release

[!IMPORTANT]
Liquibase 4.29.2 patches minor issues found in Liquibase 4.29.1 release.

[!NOTE]
See the Liquibase 4.29.2 Release Notes for the complete set of release information.

Notable Changes

[PRO]
Custom Policy Checks updates: Create and run Python-based checks which fit your specific needs.
  • Liquibase checks have been opened to the world of Python development! This release fixes some minor issues so you can use your custom Python scripts as policy checks to solve your nuanced and techstack specific conditions for better risk mitigation, compliance, code quality, security, and more.
  • Learn more https://docs.liquibase.com/custom-policy-checks
  • Get the Checks extension to enable this capability: https://docs.liquibase.com/pro-extensions

Deprecation Notice

MacOS .dmg Installer to be removed in next release.
  • This is the final Liquibase release in which the MacOS installer will be shipped. Both the tarball (the liquibase-x.y.z.tar.gz) and the .zip (liquibase-x.y.x.zip) are the preferred replaced options for MacOS users.
  • Questions or comments? https://www.liquibase.com/contact-us

[PRO] Changelog

💥 Breaking Changes

  • None

Changes

[OSS] Changelog

💥 Breaking Changes

  • None

Changes

🤖 Security, Driver and Other Updates

3 changes

New Contributors

Full Changelog: liquibase/liquibase@v4.29.1...v4.29.2

Get Certified

Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.

Read the Documentation

Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.

Meet the Community

Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:

Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team

Thanks to everyone who helps make the Liquibase community strong!

File Descriptions

  • Liquibase CLI -- Includes open source + commercial functionality
  • liquibase-x.y.z.tar.gz -- Archive in tar.gz format
  • liquibase-x.y.z.zip -- Archive in zip format
  • liquibase-windows-x64-installer-x.y.z.exe -- Installer for Windows
  • liquibase-macos-installer-x.y.z.dmg -- Installer for MacOS
  • Primary Libraries - For embedding in other software
    • liquibase-core-x.y.z.jar – Base Liquibase library (open source)
    • liquibase-commerical-x.y.z.jar – Additional commercial functionality
  • liquibase-additional-x.y.z.zip – Contains additional, less commonly used files
    • Additional libraries such as liquibase-maven-plugin.jar and liquibase-cdi.jar
    • Javadocs for all the libraries
    • Source archives for all the open source libraries
    • ASC/MD5/SHA1 verification hashes for all files

v4.29.1

Compare Source

  • Liquibase 4.29.1 patches a pom mismatch in the Liquibase BigQuery Commercial Extension.

  • Liquibase 4.29.1 resolves an issue with the zip distribution where all files were incorrectly placed inside liquibase-4.29.1 directory. This update ensures proper file organization and installation.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@yegor256
Copy link
Owner

@rultor please, try to merge, since 9 checks have passed

@rultor
Copy link
Collaborator

rultor commented Jul 31, 2024

@rultor please, try to merge, since 9 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Jul 31, 2024

@rultor please, try to merge, since 9 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 11min)

    /usr/local/rvm/rubies/ruby-3.2.2/lib/ruby/3.2.0/tmpdir.rb:94:in `mktmpdir'
    test/test_pool.rb:157:in `bootstrap'
    test/test_pool.rb:78:in `test_transaction'
\u001b[0m

bin/rails test /home/r/repo/test/test_pool.rb:77



Finished in 129.646476s, 0.0926 runs/s, 0.1157 assertions/s.
12 runs, 15 assertions, 0 failures, 1 errors, 0 skips
2024-07-31 23:38:37.738 UTC [2161] LOG:  received smart shutdown request
2024-07-31 23:38:37.739 UTC [2161] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 2161
2024-07-31 23:38:37.741 UTC [2135] LOG:  received smart shutdown request
2024-07-31 23:38:37.742 UTC [2135] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 2135
PostgreSQL killed in PID 2108
2024-07-31 23:38:37.747 UTC [2043] LOG:  received smart shutdown request
2024-07-31 23:38:37.747 UTC [2043] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 2043
2024-07-31 23:38:37.750 UTC [1978] LOG:  received smart shutdown request
2024-07-31 23:38:37.750 UTC [1978] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 1978
2024-07-31 23:38:37.753 UTC [1913] LOG:  received smart shutdown request
2024-07-31 23:38:37.753 UTC [1913] LOG:  could not open file "postmaster.pid": No such file or directory
2024-07-31 23:38:37.753 UTC [1913] LOG:  could not open file "postmaster.pid": No such file or directory
2024-07-31 23:38:37.754 UTC [1913] LOG:  performing immediate shutdown because data directory lock file is invalid
2024-07-31 23:38:37.754 UTC [1913] LOG:  received immediate shutdown request
2024-07-31 23:38:37.755 UTC [1913] LOG:  could not open file "postmaster.pid": No such file or directory
2024-07-31 23:38:37.759 UTC [1919] LOG:  could not open temporary statistics file "pg_stat/global.tmp": No such file or directory
2024-07-31 23:38:37.764 UTC [1913] LOG:  database system is shut down
PostgreSQL killed in PID 1913
PostgreSQL killed in PID 1847
PostgreSQL killed in PID 1781
PostgreSQL killed in PID 1711
PostgreSQL killed in PID 1641
PostgreSQL killed in PID 1616
Coverage report generated for Unit Tests to /home/r/repo/coverage. 178 / 194 LOC (91.75%) covered.
2024-07-31 23:38:37.808 UTC [1978] LOG:  background worker "logical replication launcher" (PID 1985) exited with exit code 1
2024-07-31 23:38:37.809 UTC [1980] LOG:  shutting down
2024-07-31 23:38:37.810 UTC [1980] PANIC:  could not open file "/tmp/test20240731-1599-v2vr66/pgsql/global/pg_control": No such file or directory
2024-07-31 23:38:37.829 UTC [2043] LOG:  background worker "logical replication launcher" (PID 2050) exited with exit code 1
2024-07-31 23:38:37.831 UTC [2045] LOG:  shutting down
2024-07-31 23:38:37.831 UTC [2045] PANIC:  could not open file "/tmp/test20240731-1599-aiumu4/pgsql/global/pg_control": No such file or directory
2024-07-31 23:38:37.866 UTC [2161] LOG:  background worker "logical replication launcher" (PID 2168) exited with exit code 1
2024-07-31 23:38:37.867 UTC [2163] LOG:  shutting down
2024-07-31 23:38:37.867 UTC [2163] PANIC:  could not open file "/tmp/test20240731-1599-kwd9mv/pgsql/global/pg_control": No such file or directory
2024-07-31 23:38:37.902 UTC [2135] LOG:  background worker "logical replication launcher" (PID 2142) exited with exit code 1
2024-07-31 23:38:37.916 UTC [2137] LOG:  shutting down
2024-07-31 23:38:37.917 UTC [2137] PANIC:  could not open file "/tmp/test20240731-1599-644o8n/pgsql/global/pg_control": No such file or directory
rake aborted!
Command failed with status (1)
/usr/local/rvm/gems/ruby-3.2.2/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/usr/local/rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:22:in `eval'
/usr/local/rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => default => test
(See full trace by running task with --trace)
container 7d82595de73c5056a6b7234f31f35404c48fdb63f866051d64e77a080906bb7c is dead
Wed Jul 31 23:39:21 UTC 2024

@renovate renovate bot force-pushed the renovate/liquibase.version branch from d430d09 to 7abdfce Compare August 22, 2024 21:03
@renovate renovate bot force-pushed the renovate/liquibase.version branch from 7abdfce to 98470fe Compare September 4, 2024 15:26
@renovate renovate bot changed the title Update dependency org.liquibase:liquibase-maven-plugin to v4.29.1 Update dependency org.liquibase:liquibase-maven-plugin to v4.29.2 Sep 4, 2024
@yegor256 yegor256 merged commit 3f4ceaf into master Sep 29, 2024
9 checks passed
@renovate renovate bot deleted the renovate/liquibase.version branch September 29, 2024 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@yegor256 @rultor