1.0.0-RC.3 on Maven Central is an accidental republish of the RC.2 code (see CHANGELOG), so the snake_case rename shipped in 1.0.0-RC.4. This fixes the spots that still tied the rename to the burned RC.3:
UPGRADE.md: heading is now "To 1.0.0-RC.4", with a note that upgrading from RC.3 is the same as from RC.2; body text and the table header ("Before (RC.1, RC.2, RC.3)" / "From RC.4") follow.
@Deprecated(since = "1.0.0-RC.4") and the "before 1.0.0-RC.4" javadoc/comments on the SqlWorkbenchQBitConfig.LEGACY_* constants, ShareAudienceType.LEGACY_NAME and the 6 entity LEGACY_TABLE_NAME constants.
CHANGELOG.md RC.4 section: "pre-RC.4 names", and "Upgrade from RC.2 (or RC.3, a copy of RC.2)". The burned RC.3 entry itself is unchanged.
README.md Upgrading row: "From RC.2 (or RC.3, a copy of RC.2)".
1.0.0-RC.3 on Maven Central is an accidental republish of the RC.2 code (see CHANGELOG), so the snake_case rename shipped in **1.0.0-RC.4**. This fixes the spots that still tied the rename to the burned RC.3:
- `UPGRADE.md`: heading is now "To 1.0.0-RC.4", with a note that upgrading from RC.3 is the same as from RC.2; body text and the table header ("Before (RC.1, RC.2, RC.3)" / "From RC.4") follow.
- `@Deprecated(since = "1.0.0-RC.4")` and the "before 1.0.0-RC.4" javadoc/comments on the `SqlWorkbenchQBitConfig.LEGACY_*` constants, `ShareAudienceType.LEGACY_NAME` and the 6 entity `LEGACY_TABLE_NAME` constants.
- `CHANGELOG.md` RC.4 section: "pre-RC.4 names", and "Upgrade from RC.2 (or RC.3, a copy of RC.2)". The burned RC.3 entry itself is unchanged.
- `README.md` Upgrading row: "From RC.2 (or RC.3, a copy of RC.2)".
- `SqlWorkbenchQBitProducerTest` naming-test comment: RC.4 / pre-RC.4.
Docs/annotation metadata only; `./mvnw verify` passes locally.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
1.0.0-RC.3 on Maven Central is an accidental republish of the RC.2 code (see CHANGELOG), so the snake_case rename shipped in 1.0.0-RC.4. This fixes the spots that still tied the rename to the burned RC.3:
UPGRADE.md: heading is now "To 1.0.0-RC.4", with a note that upgrading from RC.3 is the same as from RC.2; body text and the table header ("Before (RC.1, RC.2, RC.3)" / "From RC.4") follow.@Deprecated(since = "1.0.0-RC.4")and the "before 1.0.0-RC.4" javadoc/comments on theSqlWorkbenchQBitConfig.LEGACY_*constants,ShareAudienceType.LEGACY_NAMEand the 6 entityLEGACY_TABLE_NAMEconstants.CHANGELOG.mdRC.4 section: "pre-RC.4 names", and "Upgrade from RC.2 (or RC.3, a copy of RC.2)". The burned RC.3 entry itself is unchanged.README.mdUpgrading row: "From RC.2 (or RC.3, a copy of RC.2)".SqlWorkbenchQBitProducerTestnaming-test comment: RC.4 / pre-RC.4.Docs/annotation metadata only;
./mvnw verifypasses locally.🤖 Generated with Claude Code