chore(deps): move agent-bundle to pkg.pr.new 4f62216f30 - #103
Conversation
🦋 Changeset detectedLatest commit: 8b44b75 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8b44b75719
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| for (const [table, columns] of Object.entries(TABLE_COLUMNS)){ | ||
| const actual = transactionDb.prepare(`PRAGMA table_info(${table})`).all().map(columnSignature); | ||
| if (actual.join(',') !== columns.join(',')) throw new _65_js__rspack_import_6/* .AgentStateError */.nk('corrupt', `State '${definition.id}' table ${table} at '${this.location}' does not match the current schema (has ${actual.join(', ')}; expected ${columns.join(', ')})`); |
There was a problem hiding this comment.
Migrate existing relay databases before enforcing NOT NULL
When upgrading any profile whose relay.sqlite was initialized by the previous bundle, agent_state_journal.result_state is declared as nullable (result_state TEXT). The preceding CREATE TABLE IF NOT EXISTS does not change that schema, so this exact signature check rejects the database as corrupt because it now expects result_state NOT NULL. Since the relay always reopens this durable file, previously configured managed relays fail to start even when all stored values are valid; migrate the column or continue accepting the prior schema before enforcing the new signature.
AGENTS.md reference: AGENTS.md:L9-L11
Useful? React with 👍 / 👎.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Moves the
agent-bundleand@agent-bundle/runtimedevDependency pins to the pkg.pr.new preview at4f62216f30(agent-bundle 0.3.0 / runtime 0.2.0).Migrations:
package.jsonand regeneratedpackage-lock.jsonwithnpm install.artifact/with the new compiler (npm run build).zodis already 4.6.5 (≥4.6.4), and validate, build, artifact validation, and typecheck passed without changes.Local gate (GitHub-hosted runners are stalled, so this was not verified in CI):
npm run check: validate, build, validate:artifact, and typecheck passed. Unit tests went 406/407. The failure was a timing flake intest/codex-session.test.js("Timed out connecting to Codex app-server"). That test uses only Node built-ins and nothing from agent-bundle, and the file passed 3/3 when run alone.npm testrerun on the fresh build: 407/407 unit tests and 15/15 route tests passed.