Shared internal CLIs and scripts for Volksverpetzer's engineering team —
things every repo/teammate might need (e.g. whitelisting an IP with a cloud
provider), rather than a scripts/ folder duplicated per repo. Not
design/brand code — see vvp_design_system
for that.
packages/whitelist-ip—@volksverpetzer/whitelist-ip. Adds your current public IPv4 to a Scaleway Managed Database instance's ACL allow list.
Packages publish to the public npm registry as @volksverpetzer/* — no
.npmrc registry mapping or auth needed to install them.
npx @volksverpetzer/whitelist-ipVersioning uses Changesets,
mirroring vvp_design_system. Run pnpm changeset to describe a change;
merging to main opens a "Version Packages" PR, and merging that PR
publishes to npm.
Publishing uses Trusted Publishing
(OIDC) — no NPM_TOKEN secret. As with vvp_design_system:
- A package's first version can't go out via CI. npm requires the
package to already exist before Trusted Publishing can be configured for
it, so each new package needs one manual
npm publish(from an account with access to the@volksverpetzerscope) before this applies. - After that, go to the package's Settings → Trusted Publisher on
npmjs.com and add: repository
Volksverpetzer/vvp_tools, workflow filerelease.yml, environment left blank.