Repository navigation
chore(agbossjs/agboss#691): @agboss/postgres 0.1.1 — the version of the train, on the core's release candidate - #45
Draft
PavelRavvich wants to merge 1 commit into
Draft
PavelRavvich wants to merge 1 commit into
PavelRavvich wants to merge 1 commit into
Conversation
…he train, on the core's release candidate - package.json and package-lock.json at 0.1.1; the peer dependency stays @agboss/core ^0.1.1. - .agboss-version.json pins the core's release candidate agbossjs/agboss 58655180 (0.1.1) by commit: built, packed and tested on exactly what v0.1.1 tags. The release workflow publishes only on a registry pin, which RELEASE_CHECKLIST.md Step 6 writes once @agboss/core@0.1.1 is on npm (node scripts/pin-framework.mjs --registry 0.1.1). - CHANGELOG.md: the 0.1.1 section dated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Kh8JmysuhZyQRSpNyJdPg
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refs agbossjs/agboss#691
Draft on purpose. This merges in agbossjs/agboss
RELEASE_CHECKLIST.mdStep 6, once@agboss/core@0.1.1is on npm, together with the registry pin (node scripts/pin-framework.mjs --registry 0.1.1). The release workflow refuses to publish on a commit pin, so the registry pin has to be on this branch before it merges.What changed
@agboss/core^0.1.1is unchanged, so the published package installs on the core from npm..agboss-version.jsonpins the core's release candidate, agbossjs/agboss58655180(0.1.1), by commit.CHANGELOG.md: the 0.1.1 section is dated.How it was tested
Run locally against the capped containers, on the core packed from
58655180(AGBOSS_REPO_DIR,pack:framework,install:packed):npm run checkagainst PostgreSQL 16 on 55432: 65 files, 704 tests passed.🤖 Generated with Claude Code
https://claude.ai/code/session_012Kh8JmysuhZyQRSpNyJdPg