[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-10441":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":42,"readmeContent":43,"aiSummary":44,"trendingCount":15,"starSnapshotCount":15,"syncStatus":45,"lastSyncTime":46,"discoverSource":47},10441,"liquibase","liquibase\u002Fliquibase","Main Liquibase Source","https:\u002F\u002Fwww.liquibase.org",null,"Java",5526,1944,139,206,0,1,3,31,4,40.87,"Other",false,"main",true,[26,27,28,29,30,31,32,33,34,35,36,5,37,38,39,40,41],"continuous-delivery","continuous-deployment","database","database-administration","database-management","database-migrations","db2","devops","hacktoberfest","java","java-library","mariadb","mysql","oracle","sql","sqlserver","2026-06-12 02:02:21","# Liquibase [![Build and Test](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Factions\u002Fworkflows\u002Frun-tests.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Factions\u002Fworkflows\u002Frun-tests.yml) [![Nightly Release](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Factions\u002Fworkflows\u002Fnightly-release.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Freleases\u002Ftag\u002Fnightly) [![Quality Gate Status](https:\u002F\u002Fsonarcloud.io\u002Fapi\u002Fproject_badges\u002Fmeasure?project=liquibase&metric=alert_status)](https:\u002F\u002Fsonarcloud.io\u002Fsummary\u002Fnew_code?id=liquibase)\n\u003Cp align=\"center\">\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Fblob\u002Fmain\u002FLiquibase.png\" width=\"30%\" height=\"30%\">\u003C\u002Fp>\n\n> **Note:** This repository's default branch is `main`.\n> - **Local clones\u002Fforks:** run `git branch -m master main && git fetch origin && git branch -u origin\u002Fmain main`\n> - **CI \u002F scripts \u002F docs:** update any references to `master` (e.g., `raw.githubusercontent.com\u002Fliquibase\u002Fliquibase\u002Fmaster\u002F...`, workflow triggers, submodules) to use `main`\n\nLiquibase helps millions of developers track, version, and deploy database schema changes. It will help you to:\n- Control database schema changes for specific versions\n- Eliminate errors and delays when releasing databases\n- Automatically order scripts for deployment\n- Easily rollback changes\n- Collaborate with tools you already use\n\nThis repository contains the main source code for Liquibase Community. For more information about the product, see the [Liquibase website](https:\u002F\u002Fwww.liquibase.com\u002F).\n\n## Release Cadence and Access\n\nAt Liquibase, we believe great database change management starts with a community that can rely on a predictable and transparent release process. To support this commitment, and starting with version 5.0.2, we are providing two clear ways for the community to access updates and improvements:\n\n- **Main Branch Builds on GitHub** – Main branch builds are continuously published on GitHub, offering early access to the latest improvements and fixes as they are developed. These builds enable the community to test upcoming capabilities and provide feedback ahead of the next official release.\n- **Quarterly Community Releases** – Liquibase Community updates are released quarterly (Feb, May, Aug, Nov) providing stable, production-ready versions that allow teams to plan upgrades and maintenance with confidence. These releases are available through all standard distribution channels, including GitHub, Maven Central, package managers, container registries, and other official Liquibase Community distribution locations.\n\nTogether, these options ensure that teams can choose the path that best fits their needs - whether prioritizing stability through scheduled releases or engaging early with the latest innovations in Liquibase.\n\n### Build Access and Release Planning\n\n- **Nightly builds:** The latest Main branch build is available at https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Freleases\u002Ftag\u002Fnightly — download `liquibase-nightly.tar.gz` (Linux\u002FmacOS) or `liquibase-nightly.zip` (Windows). Updated automatically after each successful test run on main.\n- **Latest Release: v5.0.2 — March 5, 2026** \\\nhttps:\u002F\u002Fwww.liquibase.com\u002Fdownload-community\n- **Next Planned Release: May 15, 2026** \n- **Roadmap:** \\\nhttps:\u002F\u002Fgithub.com\u002Forgs\u002Fliquibase\u002Fprojects\u002F3\u002Fviews\u002F9?layout=board\n\n## Liquibase Automation and Integrations\n\nLiquibase Community has built-in support for a variety of databases. Databases that are not part of Liquibase Community require extensions that you can download for free. Here is the full list of [supported databases](https:\u002F\u002Fwww.liquibase.com\u002Fsupported-databases).\n\nLiquibase can be integrated with Maven, Ant, Gradle, Spring Boot, and other CI\u002FCD tools. For a full list, see [Liquibase Tools & Integrations](https:\u002F\u002Fdocs.liquibase.com\u002Ftools-integrations\u002Fhome.html). You can use Liquibase with [GitHub Actions](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase-github-action-example), [Spinnaker](https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase-spinnaker-plugin), and many different [workflows](https:\u002F\u002Fdocs.liquibase.com\u002Fworkflows\u002Fhome.html).\n\n\n## Install and Run Liquibase\n\n### System Requirements\nLiquibase system requirements can be found on the [Download Liquibase](https:\u002F\u002Fwww.liquibase.com\u002Fdownload) page.\n\n### An H2 in-memory database example for CLI\n1. [Download and run the appropriate installer](https:\u002F\u002Fwww.liquibase.com\u002Fdownload). \n2. Make sure to add Liquibase to your PATH.\n3. Copy the included `examples` directory to the needed location.\n4. Open your CLI and navigate to your `examples\u002Fsql` or `examples\u002Fxml` directory.\n5. Start the included H2 database with the `liquibase init start-h2` command.\n6. Run the `liquibase update` command.\n7. Run the `liquibase history` command to see what has executed!\n\nSee also how to [get started with Liquibase in minutes](https:\u002F\u002Fdocs.liquibase.com\u002Fstart\u002Fhome.html) or refer to our [Installing Liquibase](https:\u002F\u002Fdocs.liquibase.com\u002Fstart\u002Finstall\u002Fhome.html) documentation page for more details.\n\n## Documentation\n\nVisit the [Liquibase Documentation](https:\u002F\u002Fdocs.liquibase.com\u002Fhome.html) website to find the information on how Liquibase works.\n\n## Courses\n\nLearn all about Liquibase by taking our free online courses at [Liquibase University](https:\u002F\u002Flearn.liquibase.com\u002F).\n\n## Want to help?\n\nWant to file a bug or improve documentation? Excellent! Read up on our guidelines for [contributing](https:\u002F\u002Fcontribute.liquibase.com\u002F)!\n\n### Contribute code \n\nUse our [step-by-step instructions](https:\u002F\u002Fcontribute.liquibase.com\u002Fcode\u002F) for contributing code to the Liquibase project. \n\n### Join the Liquibase Community\n\nEarn points for your achievements and contributions, collect and show off your badges, add accreditations to your LinkedIn. [Learn more about the pathway to Legend and benefits](https:\u002F\u002Fwww.liquibase.com\u002Fcommunity\u002Fliquibase-legends). Enjoy being part of the community!\n\n## Liquibase Extensions\n\n[Provide more database support and features for Liquibase](https:\u002F\u002Fcontribute.liquibase.com\u002Fextensions-integrations\u002Fdirectory\u002F).\n\n## License\n\nLiquibase Community is [licensed under the Functional Source License (FSL)](https:\u002F\u002Ffsl.software\u002FFSL-1.1-ALv2.template.md).\n\n[Liquibase Secure](https:\u002F\u002Fwww.liquibase.com\u002Fliquibase-secure) has additional features and support and is commercially licensed.\n\nLIQUIBASE is a registered trademark of [Liquibase Inc.](https:\u002F\u002Fwww.liquibase.com\u002Fcompany)\n\n## [Contact us](https:\u002F\u002Fwww.liquibase.com\u002Fcontact)\n\n[Liquibase Forum](https:\u002F\u002Fforum.liquibase.org\u002F) \n\n[Liquibase Blog](https:\u002F\u002Fwww.liquibase.com\u002Fblog)\n\n[Get Support & Advanced Features](https:\u002F\u002Fwww.liquibase.com\u002Fpricing)\n\n## Publish Release Manual Trigger to Sonatype \n\n1. When a PO (Product Owner) or a Team Leader navigates to Publish a release from here -> https:\u002F\u002Fgithub.com\u002Fliquibase\u002Fliquibase\u002Freleases\u002F, the workflow from \u002Fworkflow\u002Frelease-published.yml job is triggered. \n2. When a release is triggered, the workflow file will stop after `Setup` step and an email will be sent out to the list of `approvers` mentioned in job `manual_trigger_deployment`. You can click on the link and perform anyone of the options mentioned in description. \n3. A minimum of 2 approvers are needed in order for the other jobs such as `deploy_maven`, `deploy_javadocs`, `publish_to_github_packages`, etc to be executed.\n4. When you view the GitHub PR, make sure to verify the version which is being published. It should say something like `Deploying v4.20.0 to sonatype`\n\n\n\n","Liquibase 是一个用于跟踪、版本控制和部署数据库模式变更的工具。它支持控制特定版本的数据库模式变更，减少数据库发布时的错误与延迟，并能自动排序脚本以进行部署及轻松回滚更改。基于 Java 开发，Liquibase 兼容多种数据库系统如 MySQL, PostgreSQL, Oracle 等，适用于需要持续集成\u002F部署（CI\u002FCD）环境中管理数据库变更的场景。此外，该项目提供两种更新方式：GitHub 上的主分支构建提供了对最新功能的早期访问；而季度社区版则为用户提供稳定且适合生产的版本。",2,"2026-06-11 03:28:25","top_topic"]