Upgrading

New versions, same arrangements. Everything carries forward.

How to upgrade

Run the upgrade command for your language wrapper. The Rust binary ships inside the wrapper package, so a single command upgrades everything.

pip install --upgrade goldlapel

npm update goldlapel

gem update goldlapel

go get -u github.com/goldlapel/goldlapel-go

<!-- pom.xml -->
<dependency>
    <groupId>com.goldlapel</groupId>
    <artifactId>goldlapel</artifactId>
    <version>0.1.0-rc17</version>
</dependency>

composer update goldlapel/goldlapel

dotnet add package GoldLapel --version latest

brew upgrade goldlapel

You can also download the latest binary directly from the platform pages.

What happens during an upgrade

Upgrading Gold Lapel is straightforward. Stop the old process, start the new one. There is no migration step and no downtime ceremony.

• No downtime required. Stop the old process, start the new one. Your application reconnects automatically.
• Materialized views and indexes are preserved. They live in the _goldlapel schema inside PostgreSQL, not in the proxy. The new version picks them up on startup.
• Configuration carries forward. Your goldlapel.toml is unchanged. New settings use sensible defaults until you choose to configure them.
• The dashboard confirms the upgrade. The Overview tab shows the running version. If a newer version is available, an upgrade banner appears with the correct command for your package manager.

Version history

Gold Lapel is in active development, currently at 0.1.0-rc17. We publish release candidates as the feature set stabilizes toward a 1.0 release.

A full changelog will be published alongside the 1.0 release. In the meantime, the dashboard's upgrade banner includes a summary of what changed in each new version.

Rolling back

If you need to return to a previous version, the process is the same in reverse: stop the current process and install the older version.

pip install goldlapel==0.1.0-rc16

npm install goldlapel@0.1.0-rc16

brew install goldlapel@0.1.0-rc16

There are no database migrations to reverse. Gold Lapel does not modify your schema. The materialized views and indexes it creates are additive, managed entirely within the _goldlapel schema, and compatible across versions.