Repository navigation
Release 0.5.1: fixes from two applications adopting 0.5.0 - #102
Merged
Merged
Conversation
pgstencil create wrote into the last configured source without checking, so a project whose sources were all package directories got a new SQL file inside node_modules. It now refuses any target inside node_modules. status, validate and migrate gain --also <dir> for a source only some databases get, and --require-database-url to fail rather than fall back to the development database. They refuse a DATABASE_URL that is set but empty, which is how a workflow sees a lost secret. reset refuses to run while DATABASE_URL is set. Every command takes --env-file and --env-file-if-exists. These are what kept both applications on their own migration scripts. The default sign-in sender is a valid address literal for an IP origin, and emailFrom is trimmed. pgstencil/email exports the email module without the root's node:crypto import, for code a browser also loads, and the package declares sideEffects: false. The changelog's 0.5.0 entry gains the notes it was published without: the stripe 23 and Stripe API version move, the Better Auth pin, and the optional tooling peers from 0.4.0. Co-Authored-By: Claude Fable 5.2 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
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.
Fixes and compatible additions found while two applications adopted 0.5.0, with the version raised to 0.5.1 in the same PR so the audited commit is the released one.
Fixed
pgstencil createcould write into an installed package. With only package directories configured as sources, it created a SQL file insidenode_modules. It now refuses any target insidenode_modules.DATABASE_URLthat is set but empty is refused bystatus,validateandmigrate. 0.5.0 passed the empty string to the driver. An empty value is how a workflow sees a lost secret.pgstencil resetrefuses to run whileDATABASE_URLis set; it only ever recreates the development database.signin@[127.0.0.1]), andemailFromis trimmed.Added
--also <dir>and--require-database-urlonstatus,validateandmigrate, and--env-file/--env-file-if-existson every command. These are what kept both applications on their own migration scripts.pgstencil/emailsubpath, which exports the email module without the root'snode:cryptoimport, and"sideEffects": falseon the core package.Verification
On this branch under the pinned Node:
pnpm check(189 tests),pnpm db:verifyandpnpm packages:verifywith the 0.5.1 archives all pass.Merging stages the three packages on npm once
security-auditpasses on the merge commit. Nothing is public until each is approved with 2FA.🤖 Generated with Claude Code