chore(changepacks): bump every published crate at the same Minor level

[owjs3901]

문제

Update Versions PR (#177) 의 CI 가 거의 모든 잡에서 실패한다.

error: failed to select a version for the requirement `vespertide-core = "=0.2.1"`
candidate versions found which didn't match: 0.3.0
required by package `vespertide v0.2.2`

원인

0.2.1 -> 다음 릴리스에 쌓인 changepack 5개가 크레이트마다 서로 다른 레벨을 지정했다.

크레이트	레벨	결과 버전
core, query, planner, cli, config, exporter, naming	Minor	0.3.0
lsp	Patch	0.2.2
vespertide, loader, macro	(changepack 없음, 의존 전파만)	0.2.2

버전이 갈라지면서 루트 [workspace.dependencies] 의 정확 핀(version = "=0.2.1")이 갱신되지
않았고, vespertide 0.2.2 가 vespertide-core = "=0.2.1" 을 요구하는데 실제로는 0.3.0 만 존재해
워크스페이스 해석이 깨졌다. build 가 죽으니 test / clippy / doc / coverage 등 후속 잡이 모두 실패한다.

직전 성공 릴리스(2ee302c Update Versions)는 changepack 하나가 12개 패키지를 동일 레벨로 올렸고,
그때는 루트 Cargo.toml 의 핀 9개가 함께 갱신되어 문제가 없었다.

변경

published 크레이트 11개 전부를 Minor 로 올리는 changepack 하나를 추가한다.
changepack 은 패키지별로 가장 높은 레벨이 채택되므로, 기존 5개와 합쳐지면 모든 크레이트가
0.3.0 으로 정렬되고 루트 핀도 =0.3.0 으로 함께 갱신된다.

대상: cli, config, core, exporter, loader, lsp, macro, naming, planner, query, vespertide
(vespertide-schema-gen 은 .changepacks/config.json 에서 제외된 패키지라 대상 아님.
apps/vscode-extension 은 이번 릴리스에 코드 변경이 없어 포함하지 않았다.)

확인

머지 후 Update Versions PR 이 재생성되면서

• 11개 크레이트가 모두 0.3.0
• 루트 [workspace.dependencies] 핀이 모두 =0.3.0

이 되는지, 그리고 #177 의 CI 가 green 으로 돌아오는지 확인이 필요하다.

[github-actions]

Changepacks

vespertide@0.2.1 → 0.3.0 - crates/vespertide/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.

vespertide-cli@0.2.1 → 0.3.0 - crates/vespertide-cli/Cargo.toml

Minor

• modify_column_type.fill_with 를 bare enum 라벨로 확정 (스키마 문서와 구현 불일치로 enum 축소 마이그레이션이 invalid input value for enum 으로 실패하던 문제). 따옴표가 이미 붙은 기존 값은 한 겹 제거 + 1회 경고로 하위호환 유지
• data_migration 액션 추가: MigrationAction::DataMigration(#[non_exhaustive]라 additive), DataMigrationSql/leading_ddl_keyword/sql_preview 공개 API 신설, DDL 가드용 PlannerError::DataMigrationContainsDdl 변형 추가(PlannerError는 exhaustive라 0.x 기준 breaking), find_raw_sql_replay_hazards 신설, diff/status의 raw_sql 리플레이 경고
• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• Prisma ORM exporter 추가

vespertide-config@0.2.1 → 0.3.0 - crates/vespertide-config/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• 성능 최적화 웨이브: 미사용 public API 정리(NameCase::is_*, EnumValues::variant_names/to_sql_values, sql::helpers 일부, find_primary_key_removals 시그니처)와 Orm::Prisma 변형 추가로 0.x 기준 breaking

vespertide-core@0.2.1 → 0.3.0 - crates/vespertide-core/Cargo.toml

Minor

• modify_column_type.fill_with 를 bare enum 라벨로 확정 (스키마 문서와 구현 불일치로 enum 축소 마이그레이션이 invalid input value for enum 으로 실패하던 문제). 따옴표가 이미 붙은 기존 값은 한 겹 제거 + 1회 경고로 하위호환 유지
• data_migration 액션 추가: MigrationAction::DataMigration(#[non_exhaustive]라 additive), DataMigrationSql/leading_ddl_keyword/sql_preview 공개 API 신설, DDL 가드용 PlannerError::DataMigrationContainsDdl 변형 추가(PlannerError는 exhaustive라 0.x 기준 breaking), find_raw_sql_replay_hazards 신설, diff/status의 raw_sql 리플레이 경고
• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• 성능 최적화 웨이브: 미사용 public API 정리(NameCase::is_*, EnumValues::variant_names/to_sql_values, sql::helpers 일부, find_primary_key_removals 시그니처)와 Orm::Prisma 변형 추가로 0.x 기준 breaking

vespertide-exporter@0.2.1 → 0.3.0 - crates/vespertide-exporter/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• 성능 최적화 웨이브: 미사용 public API 정리(NameCase::is_*, EnumValues::variant_names/to_sql_values, sql::helpers 일부, find_primary_key_removals 시그니처)와 Orm::Prisma 변형 추가로 0.x 기준 breaking
• Prisma ORM exporter 추가

vespertide-loader@0.2.1 → 0.3.0 - crates/vespertide-loader/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.

vespertide-lsp@0.2.1 → 0.3.0 - crates/vespertide-lsp/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.

Patch

• data_migration 액션 추가: MigrationAction::DataMigration(#[non_exhaustive]라 additive), DataMigrationSql/leading_ddl_keyword/sql_preview 공개 API 신설, DDL 가드용 PlannerError::DataMigrationContainsDdl 변형 추가(PlannerError는 exhaustive라 0.x 기준 breaking), find_raw_sql_replay_hazards 신설, diff/status의 raw_sql 리플레이 경고

vespertide-macro@0.2.1 → 0.3.0 - crates/vespertide-macro/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.

vespertide-naming@0.2.1 → 0.3.0 - crates/vespertide-naming/Cargo.toml

Minor

• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• Prisma ORM exporter 추가

vespertide-planner@0.2.1 → 0.3.0 - crates/vespertide-planner/Cargo.toml

Minor

• data_migration 액션 추가: MigrationAction::DataMigration(#[non_exhaustive]라 additive), DataMigrationSql/leading_ddl_keyword/sql_preview 공개 API 신설, DDL 가드용 PlannerError::DataMigrationContainsDdl 변형 추가(PlannerError는 exhaustive라 0.x 기준 breaking), find_raw_sql_replay_hazards 신설, diff/status의 raw_sql 리플레이 경고
• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• 성능 최적화 웨이브: 미사용 public API 정리(NameCase::is_*, EnumValues::variant_names/to_sql_values, sql::helpers 일부, find_primary_key_removals 시그니처)와 Orm::Prisma 변형 추가로 0.x 기준 breaking

vespertide-query@0.2.1 → 0.3.0 - crates/vespertide-query/Cargo.toml

Minor

• modify_column_type.fill_with 를 bare enum 라벨로 확정 (스키마 문서와 구현 불일치로 enum 축소 마이그레이션이 invalid input value for enum 으로 실패하던 문제). 따옴표가 이미 붙은 기존 값은 한 겹 제거 + 1회 경고로 하위호환 유지
• add_column.fill_with가 사용자 SQL 표현식을 훼손하던 버그 수정: fill_with는 raw SQL 표현식 슬롯이므로 DEFAULT 정규화(convert_default_for_backend)를 태우지 않고 그대로 방출한다. parse_pg_type_cast도 첫 번째 :: 대신 따옴표/괄호를 건너뛴 마지막 top-level :: 에서 분리하도록 수정. 동작 변경: PostgreSQL은 fill_with를 항상 원문 그대로 방출하므로 NOW()가 더 이상 CURRENT_TIMESTAMP로 치환되지 않는다(MySQL/SQLite는 유지)
• data_migration 액션 추가: MigrationAction::DataMigration(#[non_exhaustive]라 additive), DataMigrationSql/leading_ddl_keyword/sql_preview 공개 API 신설, DDL 가드용 PlannerError::DataMigrationContainsDdl 변형 추가(PlannerError는 exhaustive라 0.x 기준 breaking), find_raw_sql_replay_hazards 신설, diff/status의 raw_sql 리플레이 경고
• align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.
• 성능 최적화 웨이브: 미사용 public API 정리(NameCase::is_*, EnumValues::variant_names/to_sql_values, sql::helpers 일부, find_primary_key_removals 시그니처)와 Orm::Prisma 변형 추가로 0.x 기준 breaking