Update Versions by github-actions[bot] · Pull Request #177 · dev-five-git/vespertide

github-actions · 2026-08-15T10:52:01Z

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

cargo-semver-checks 게이트는 PR이 도입한 changepack에서만 release-type을 도출한다 (base에 이미 있는 descriptor는 게이트를 완화하지 않는다). 이 PR에는 descriptor가 없어 게이트가 Cargo.toml 버전(0.2.1, 미변경)만 보고 아래 5건을 breaking으로 차단하고 있었다. - vespertide-config: NameCase::is_snake / is_camel / is_pascal 제거 - vespertide-core: EnumValues::variant_names / to_sql_values 제거 - vespertide-exporter: 비-non_exhaustive enum Orm에 Prisma 변형 추가 - vespertide-planner: find_primary_key_removals 인자 2 -> 1 - vespertide-query: sql::helpers의 build_schema_statement / build_query_statement / apply_column_type_with_table / build_sqlite_enum_check_clause / extract_check_clauses 제거 전부 의도된 변경이므로 되돌리지 않고 0.x 기준 breaking(Minor)으로 선언한다. 0.x에서는 Minor가 cargo-semver-checks의 major에 대응하므로 게이트가 열린다. 미선언 크레이트는 changepacks가 patch로 자동 승계한다(#177 참고). 검증: `cargo semver-checks --release-type major`로 9개 크레이트 전부 "no semver update required" (exit 0).

github-actions · 2026-08-20T15:14:23Z

Changepacks