Files
poli0981andClaude Opus 5.5 dc4cd06cbb ci: build both packages, and publish to three stores from isolated jobs
- ci.yml: the Firefox package is built and checked beside the Chrome one.
- release.yml: three release files — the Chromium package (Chrome Web Store
  and Edge Add-ons), the Firefox package and AMO's sources archive — each
  staged by exact name so a missing one fails the run, both manifests checked
  against the tag, SHA256SUMS over all three.
- One store job per store (docs/12 §3), each off until its repo variable is
  true, each in its own GitHub Environment holding only its own secrets, each
  checking the downloaded file against SHA256SUMS before uploading. They
  install tools/publish — publish-browser-extension 6.2.0 and its three
  dependencies, from their own lockfile, scripts off — instead of the ~320
  packages of the dev toolchain, which the single old job installed next to
  four Chrome secrets.
- The old job could not have worked: it sent CWS API v1.1 credentials, and
  v1.1 was shut down on 2026-10-15. store-chrome uses v2 (publisher id and a
  service account) and sets CHROME_API_VERSION explicitly. store-firefox is
  listed and desktop-only; store-edge sends the Chromium package.
- Dependabot watches tools/publish; the licence gate reads its lockfile too.
- qodana.yaml: clean since the first run's findings were handled, so any new
  one now fails that (non-required) workflow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 22:10:35 +07:00

89 lines
3.1 KiB
YAML

# docs/12 §5. Two ecosystems: the npm dev toolchain, and the pinned actions in
# .github/workflows/.
#
# Note what this file cannot do: Dependabot *security* updates run from the
# repo's alerts regardless of any config here, and they ignore `cooldown`.
# BookmarkMagic has zero runtime dependencies, so `npm audit --omit=dev`
# reports 0 and an advisory against the dev toolchain never reaches the
# published extension (docs/09 T5).
#
# `.npmrc` sets `min-release-age=7`, the same rule as `cooldown` below, for
# installs made by hand. A security PR for a version younger than 7 days can
# therefore fail to resolve until that version ages — the price of not being
# the first to install a compromised release. `npm ci` is unaffected: it
# installs whatever the lockfile pins.
version: 2
updates:
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
day: monday
open-pull-requests-limit: 5
# Supply-chain cooldown (docs/01 §6): only propose releases that have been
# public for a week.
cooldown:
default-days: 7
commit-message:
# Conventional Commits — docs/10 §7 applies to bot commits too.
prefix: chore
prefix-development: chore
include: scope
groups:
# One PR per week for the routine churn, so CI runs once rather than
# eight times and the review is a single diff.
dev-minor-and-patch:
dependency-type: development
update-types:
- minor
- patch
# WXT is 0.x, so its "minor" is semver's breaking slot, and every WXT
# bump needs the BUILT manifest diffed by hand (docs/15 decision log,
# 2026-08-03). It gets its own PR so it can never ride along unseen.
exclude-patterns:
- 'wxt'
- '@wxt-dev/*'
ignore:
# The TypeScript pair is held on purpose (docs/01 §2): `@typescript/native`
# is the TS 7 `tsc`, `typescript` is the TS 6 API that svelte-check needs.
# A major on either is a documented decision, not a weekly bump.
- dependency-name: typescript
update-types: [version-update:semver-major]
- dependency-name: '@typescript/native'
update-types: [version-update:semver-major]
# Tracks the Node major in .nvmrc (docs/01 §2), so it moves with Node.
- dependency-name: '@types/node'
update-types: [version-update:semver-major]
# The store-upload tool release.yml installs on its own (docs/12 §3): four
# packages, kept apart from the toolchain because they run beside store
# credentials. Its own directory, so its bumps arrive as their own PRs.
- package-ecosystem: npm
directory: /tools/publish
schedule:
interval: weekly
day: monday
open-pull-requests-limit: 2
cooldown:
default-days: 7
commit-message:
prefix: chore
prefix-development: chore
include: scope
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
day: monday
open-pull-requests-limit: 3
cooldown:
default-days: 7
commit-message:
prefix: ci
include: scope
groups:
actions:
patterns: ['*']