-
Notifications
You must be signed in to change notification settings - Fork 1
refactor(metaschema-modules): define events_module.record_error inline, drop the alteration #127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
12 changes: 0 additions & 12 deletions
12
...y/schemas/metaschema_modules_public/tables/events_module/alterations/add_record_error.sql
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -98,4 +98,3 @@ schemas/metaschema_modules_public/tables/image_module/table [schemas/metaschema_ | |
| schemas/metaschema_modules_public/tables/repository_module/table [schemas/metaschema_modules_public/schema] 2026-08-15T01:00:00Z devin <[email protected]> # add repository_module config table (repositories, events, workflows, builds, local change requests) | ||
| schemas/metaschema_modules_public/tables/machine_module/table [schemas/metaschema_modules_public/schema] 2026-08-15T02:00:00Z devin <[email protected]> # add machine_module config table (enrolled machines, sessions, command ledger) | ||
| schemas/metaschema_modules_public/tables/cluster_module/table [schemas/metaschema_modules_public/schema] 2026-08-17T00:00:00Z devin <[email protected]> # add cluster_module config table (fleet catalog: clusters, database servers, physical databases, placements) | ||
| schemas/metaschema_modules_public/tables/events_module/alterations/add_record_error [schemas/metaschema_modules_public/tables/events_module/table] 2026-09-06T02:30:00Z devin <[email protected]> # add record_error: the generated function that records a refused operation under its error code as the event name | ||
8 changes: 0 additions & 8 deletions
8
...t/schemas/metaschema_modules_public/tables/events_module/alterations/add_record_error.sql
This file was deleted.
Oops, something went wrong.
Binary file modified
BIN
-503 Bytes
(100%)
packages/metaschema-modules/sql/metaschema-modules--0.44.1.bundle.tar.gz
Binary file not shown.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 0 additions & 7 deletions
7
...y/schemas/metaschema_modules_public/tables/events_module/alterations/add_record_error.sql
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 bug · medium
Mutate released v0.44.1 artifact without version bump
The released
v0.44.1(tag) shippedsql/metaschema-modules--0.44.1.sqlending inALTER TABLE ... ADD COLUMN record_error, but this PR regenerates that same0.44.1artifact withrecord_errorfolded into theCREATE TABLE(sql/metaschema-modules--0.44.1.sql:365) whilepackage.jsonandmetaschema-modules.controlstill declare0.44.1. The same version now maps to two different install artifacts with different sha256 digests, breaking byte reproducibility and version immutability for consumers who pinned or installedv0.44.1. The installed schema is functionally identical, so there is no data loss, but the change should ship as a new version rather than mutating the released artifact.📋 Prompt for AI Agents
In packages/metaschema-modules, bump the version from 0.44.1 to 0.44.2 in package.json (line 3) and metaschema-modules.control (default_version), and regenerate sql/metaschema-modules--0.44.2.sql plus its .bundle.tar.gz from deploy/ + pgpm.plan, leaving the released 0.44.1 artifact untouched so consumers who installed v0.44.1 keep a stable, byte-reproducible artifact.