1building '/nix/store/hr7kw3j7hr6zcs22a13rk7hpndp2ns51-effect-release-packages-env.drv'...2CI-RUN-CONTEXT: branch=main is_main=true3RELEASE-CLONE-START: https://github.com/cameronraysmith/vanixiets.git 641ea7a1aebb00276d96a1afc2953321424ef3884RELEASE-PACKAGES-ACTION: release5packages discovered: [{"name":"docs","path":"packages/docs"}]6RELEASE-PACKAGE-ITERATION: packages/docs7running semantic-release in packages/docs...8[4:06:06 PM] [[secure]] › ℹ Running [secure] version 25.0.99[4:06:07 PM] [[secure]] › ✔ Loaded plugin "verifyConditions" from "@[secure]/changelog"10[4:06:07 PM] [[secure]] › ✔ Loaded plugin "verifyConditions" from "@[secure]/github"11[4:06:07 PM] [[secure]] › ✔ Loaded plugin "prepare" from "@[secure]/changelog"12[4:06:07 PM] [[secure]] › ✔ Loaded plugin "publish" from "@[secure]/github"13[4:06:07 PM] [[secure]] › ✔ Loaded plugin "addChannel" from "@[secure]/github"14[4:06:07 PM] [[secure]] › ✔ Loaded plugin "success" from "@[secure]/github"15[4:06:07 PM] [[secure]] › ✔ Loaded plugin "success" from "[secure]-major-tag"16[4:06:10 PM] [[secure]] › ✔ Run automated release from branch main on repository https://github.com/cameronraysmith/vanixiets.git17[4:06:11 PM] [[secure]] › ✔ Allowed to push to the Git repository18[4:06:11 PM] [[secure]] › ℹ Start step "verifyConditions" of plugin "@[secure]/changelog"19[4:06:11 PM] [[secure]] › ✔ Completed step "verifyConditions" of plugin "@[secure]/changelog"20[4:06:11 PM] [[secure]] › ℹ Start step "verifyConditions" of plugin "@[secure]/github"21[4:06:11 PM] [[secure]] [@[secure]/github] › ℹ Verify GitHub authentication22[4:06:12 PM] [[secure]] › ✔ Completed step "verifyConditions" of plugin "@[secure]/github"23[4:06:12 PM] [[secure]] › ℹ Found git tag @vanixiets/docs-v0.7.0 associated with version 0.7.0 on branch main24[4:06:12 PM] [[secure]] › ℹ Found 355 commits since last release25[4:06:12 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"26[4:06:12 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Start step "analyzeCommits" of plugin "@[secure]/commit-analyzer"27[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Found 22 commits for package @vanixiets/docs since last release28[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(ci): describe the effects registry and the docs-preview check run2930Change-Id: I64edace62e88789f23958d95fd5881805f636c2531[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release32[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(ci): describe main-only effects, rehearsals and PR previews3334Update the contributing, reference and traceability pages, the research35notes and the rollup-landing ADR (superseded-in-part notes) for the36main-only effect model, and point the path-scope-plugin-releases change37at the release-rehearsal check.3839Change-Id: Ie0d5d0d20bc7e0fc4ab94dc1fd37ca29e42fe97340[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release41[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(effects): run nixbot effects only on pushes to main4243Effects held deploy secrets while running pull-request code, and with44effects_branches = ["*"] the gitea-mq batch build claimed them first, so45main's fast-forward only replayed their statuses: docs were never46promoted and nothing was released after 0.7.0.4748- nixbot.toml: effects_on_pull_requests = false, no effects_branches;49 PR and batch builds build each effect's dependencies as the required50 nixbot/effects check51- effectRunContext.mainOnlyGuard: skip (exit 0) unless nixbot's id token52 says push to refs/heads/main; token errors fail53- deploy-docs: one path, wrangler deploy of the nix payload, superseded54 skip, lock; release-packages: one path, superseded skip, lock55- onEvent.pull_request.deploy-docs-preview: PR previews from main's code,56 using the payload nixbot built, with an assets-only config57- hermetic release-rehearsal and deploy-docs-rehearsal checks, in the58 effects' inputs so the pre-merge gate runs the real programs59- [secure]: success = {} so [secure]-major-tag runs60 outside the monorepo wrapper (ADR-0006 floating tags were never made)61- nixbot prApproval for OWNER/MEMBER/COLLABORATOR; drop SOPS_AGE_KEY and62 buildbot wiring from the vanixiets effects secrets63- remove preview-version and the legacy deploy-production script6465Change-Id: I39db5b0c6172dcb0f7e84c92a8983bf482a541ff66[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch67[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update vitest monorepo to ^5.0.268[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release69[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @[secure]/github to ^12.0.1070[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release71[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update cloudflare-workers-tooling72[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release73[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency sharp to ^0.35.574[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release75[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: Update dependency @types/node to ^26.6.376[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release77[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update cloudflare-workers-tooling78[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release79[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(deps): update astro80[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch81[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(renovate): group astro with starlight, and regenerate the tree8283@astrojs/starlight 0.42.2 declares hard peers on astro ^7.2.10 and84@astrojs/markdown-remark ^7.3.0. The tree pinned astro 7.2.9 and85@astrojs/markdown-remark ^7.2.4, so PR #2913 did not merely conflict, it86produced a tree that cannot build: "@astrojs/markdown-remark is too old to87render .mdx files ... a ^ range on an older version will not pick it up".88Renovate's built-in monorepo preset groups astro with @astrojs/* because they89share withastro/astro; starlight lives in withastro/starlight, so it arrives90alone, and arriving alone is what breaks the build. The grouping criterion that91matters is a shared peer-dependency floor, not a shared upstream repository.9293The new rule covers astro and @astrojs/**. That pattern takes in94@astrojs/cloudflare, which has peers on both astro ^7.2.0 and wrangler95^4.125.0 and therefore straddles this group and cloudflare-workers-tooling.96A dependency cannot be in two groups, so the outcome is made deliberate rather97than incidental: applyPackageRules iterates packageRules in array order and98merges each match over the accumulated config, last match winning for a scalar99like groupName (lib/util/package-rules/index.ts), so this rule is placed after100the cloudflare rule and the astro group wins. That is the right winner here --101the astro peer floor breaks the build on an ordinary minor bump, whereas the102wrangler floor is a caret range any 4.x satisfies. Note that103cloudflare-workers-tooling matches only the exact names wrangler and104@cloudflare/vite-plugin today, so no dependency actually changes group105membership; the ordering guards the case where someone later broadens it.106107Grouping alone would only relabel the open PRs, so the artifacts are108regenerated with `just bun-update-latest-stable`, superseding #2881, #2913 and109#2910 with a tree that resolves and builds:110111 @astrojs/cloudflare 14.2.5 -> 14.3.2112 @astrojs/markdown-remark ^7.2.4 -> ^7.3.1113 @astrojs/starlight 0.41.10 -> 0.42.2114 astro 7.2.9 -> 7.3.3115 @cloudflare/vite-plugin ^1.54.2 -> ^1.57.0116 wrangler ^4.127.1 -> ^4.136.0117118One bump was reverted by hand. `bun update --latest` has no knowledge of119renovate's holds, so it took conventional-changelog-conventionalcommits from120^9.3.1 to ^10.4.0, straight through the allowedVersions "<10" this config121carries because [secure]@25's bundled release-notes-generator cannot122resolve conventional-changelog-writer@9. Both package.json files were put back123to ^9.3.1 before bun.lock and bun.nix were regenerated.124125The flake-is-version-ceiling invariant survives: the re-pin phase is126load-bearing and `just bun-drift-check` reports "playwright in sync at 1.63.0"127afterwards. `just docs-build` completes (84 pages) and `just docs-test` passes12820 unit and 27 e2e tests across chromium, firefox and webkit; the hermetic129packages.vanixiets-docs build from the regenerated bun.nix also passes.130131Change-Id: Ifcd52bda1c1bd2b413c6d77e934e9b2b6a6a6964132[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch133[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: feat(docs): run firefox and webkit in the hermetic e2e check134135The linux e2e check ran chromium only, against a browser tree synthesised136from nixpkgs chromium rather than the one playwright ships. Both facts137rested on one premise: that Chrome-for-Testing binaries crash in the nix138build sandbox. A six-arm differential experiment on x86_64-linux DISPROVED139that premise - every arm using the Chrome-for-Testing chromium succeeded.140The single real sandbox failure was WebKit, which aborts with "Could not141create EGL display: no supported platform available" because there is no142/dev/dri and playwright-web-flake ships no software EGL vendor.143144So the nixpkgs-chromium wrapper is removed outright, together with the145latent source-build path it dragged in (chromium-unwrapped was in the146check's build closure, one cache miss away from compiling chromium from147source inside a docs test). Do not reintroduce it: the rationale it was148built on is not true. The actual fix is two environment variables pointing149libglvnd at mesa's llvmpipe vendor JSON.150151Coverage is now platform-split, in the project list only; no spec is152deleted, skipped, or weakened:153154 x86_64-linux chromium + firefox + webkit 27 passed155 aarch64-darwin chromium + webkit 18 passed156157WebKit is net-new coverage on darwin. Firefox is excluded there because it158cannot launch inside a darwin nix build - "Failed to launch the browser159process / *** You are running in headless mode. / Could not find profile160folder." The darwin sandbox (this host builds with sandbox = false),161concurrency (reproduced at workers = 1) and HOME (reproduced with a stable162/private/tmp HOME) were each ruled out by experiment, and the same firefox163binary from the same browsers tree passes outside the build: nix develop -c164just docs-test is 27/27 green including all nine firefox specs. The gap is165a launch defect of the darwin build environment, not a product defect, and166firefox on darwin stays covered by the devShell path.167168Worker count now follows NIX_BUILD_CORES instead of a fixed 3, with the169RAM arithmetic recorded beside it, and playwright.config.ts takes its170project and worker selection from PLAYWRIGHT_PROJECTS / PLAYWRIGHT_WORKERS171rather than inferring a chromium-only run from CI.172173Change-Id: I241ce979d6ff2e21cbdeddc96cf6db2d6a6a6964174[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is minor175[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: feat(playwright): pin playwright-web-flake to a fork tag at 1.63.0176177The playwright-web-flake input was pinned to a fork *branch*, which turned178every semantic version bump into an untitled lock-hash bump. `nix flake update`179chased the branch head, so the flake-updater bot produced #3097 -- a180three-line flake.lock diff that silently carried playwright 1.61.1 -> 1.62.1181with no corresponding npm change and nothing in its title saying a version had182moved. Renovate could not catch it either: its regex manager captured183currentValue = "fix-webkit-darwin-mac15-arm64", which is not a version, so it184never opened a PR for the flake ref at all.185186The two halves must move together. pkgs/by-name/vanixiets-docs/package.nix187materialises PLAYWRIGHT_BROWSERS_PATH directories named from the flake188driver's browsers.json revision, while the npm playwright-core resolves them189from its own bundled revision. #3097 supplied chromium-1234 to an npm190playwright that looked up chromium-1228, and all nine Chromium specs failed to191launch in 25 seconds.192193This change moves both halves at once, and closes the hole that let them194separate:195196 flake.nix -> github:cameronraysmith/playwright-web-flake/1.63.0-mac26.2197 flake.lock -> dad87258e45f8a4bc606de26438e7e4eb3733bb6198 packages/docs -> playwright and @playwright/test 1.63.0, derived from the199 flake by `just bun-repin-playwright` rather than typed in,200 so the flake stays the version ceiling201 bun.lock/bun.nix -> regenerated202203The tag is 1.63.0-mac26.2, not the earlier -mac26.1: mac26.1 fails to build204WebKit on x86_64-linux. autoPatchelfHook hard-errors with205206 auto-patchelf could not satisfy dependency libmanette-0.2.so.0 wanted by207 .../libWPEWebKit-2.0.so.1.12.0208209because playwright-driver/webkit.nix omitted libmanette (the WPE gamepad210dependency) from its Linux buildInputs. mac26.2 adds it, and nothing else211changes: playwright-driver.version is still exactly 1.63.0, so the npm pins212and the browsers.json revisions are untouched and `just bun-drift-check`213stays green. Fixing this on the flake side rather than pruning WebKit keeps214the Linux devShell -- and any hermetic check that later adopts the full215browser set -- able to realise all three browsers from binary substitution.216217The fork tag is a -mac26.<n> suffix rather than a bare 1.63.0: a bare reuse218would shadow upstream's own tag for a different tree and make the eventual219fork-drop ambiguous. The suffix sorts after the upstream base under semver and220leaves room for patch respins such as this one. It is a tag, not a branch, so221the ref no longer moves under the lock.222223Change-Id: Ie9a818bc08778ddb72994505691ab4616a6a6964224[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is minor225[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update vitest monorepo to v5226[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release227[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @types/node to ^26.6.2228[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release229[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update bun to v1.4.2230[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release231[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency starlight-links-validator to v0.26.0232[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release233[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @biomejs/biome to ^2.5.14234[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release235[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(tutorials): note the hm-sops-bridge alternative to manual age keys236237The manual age-key steps remain correct for users a host does not enroll, so238they stay; the caveat records that an enrolled user gets the key delivered to239/run/secrets/<id>-age-key at mode 0400 with home-manager's sops.age.keyFile240already pointed at it, and that assigning that option in a user module on such241a host is an evaluation conflict rather than an override.242243Change-Id: Ic29418c4d29895d49a44ba0a3729e8536a6a6964244[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release245[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(sops): drop manual age-key provisioning for bridged NixOS hosts246247The hm-sops-bridge module exists to eliminate hand-provisioning248~/.config/sops/age/keys.txt on each NixOS host, but the host and user249onboarding guides still instructed exactly that step for NixOS, and the250user-module example set sops.age.keyFile at ordinary priority, which the251bridge's own assignment turns into an evaluation conflict rather than an252override. Correct only the NixOS-side occurrences; the darwin steps,253the darwin troubleshooting section, the darwin success criteria and the254operator-workstation prerequisite are unchanged because darwin keeps the255XDG key file.256257Record next to the bridge what was measured rather than inferred: all six258NixOS hosts evaluate sops.useSystemdActivation, services.userborn.enable259and systemd.sysusers.enable to false, so the fleet is uniformly in260activation-script mode where setupSecrets runs after the users and groups261snippets and ordering relative to home-manager is free. srvos's userborn262definition is suppressed because every isNormalUser gets263autoSubUidGidRange = mkDefault true, which falsifies srvos's mkIf guard.264Also record the systemd-mode ordering race that would become possible if265the fleet flipped, and that the module has no OpenSpec change and no ADR.266267Change-Id: I9086324222cf9478566dbc91d11518286a6a6964268[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release269[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(omnigent): amend-plan270271Change-Id: Iba87725b2659d34afc07148ad10863d86a6a6964272[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release273[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(openspec): archive pyrite-niri-second-session and sync its spec274275niri is offered as a second selectable session under GDM, with GNOME276still the default and the lockable fallback. Verdict is PASS WITH277WARNINGS against an amended requirement.278279The GNOME-reachability requirement was narrowed after CAM-66 produced an280actual counterexample: niri v26.04 has no leader-death lifecycle bridge,281so a display-manager restart taken while a niri session is live strands282the compositor and blocks the next login. That is upstream behaviour no283configuration here supplies, so the requirement was miswritten rather284than the implementation deficient. Registration, selectability and285default-without-recorded-choice stand unchanged.286287Warnings carried into the corpus: 8.3-8.5 discharged by evaluation288rather than observation; 8.6 declined under CAM-59; 8.2's no-history289half is a method limitation, source-read only, because demonstrating it290would have destroyed the operator's real session preference.291292Closes CAM-63.293294Change-Id: I93baed981453f03d7485a8f998a1efca6a6a6964295[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release296[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analysis of 22 commits complete: minor release297[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Completed step "analyzeCommits" of plugin "@[secure]/commit-analyzer"298[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"299[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"300[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/release-notes-generator" does not provide step "analyzeCommits"301[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"302[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"303[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/changelog" does not provide step "analyzeCommits"304[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"305[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"306[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/github" does not provide step "analyzeCommits"307[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"308[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"309[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "[secure]-major-tag" does not provide step "analyzeCommits"310[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"311[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"312[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins313[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"314[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"315[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins316[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"317[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"318[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins319[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"320[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"321[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins322[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"323[4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"324[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins325[4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]"326[4:06:14 PM] [[secure]] › ℹ The next release version is 0.8.0327[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"328[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/commit-analyzer" does not provide step "generateNotes"329[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"330[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"331[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Start step "generateNotes" of plugin "@[secure]/release-notes-generator"332[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Found 22 commits for package @vanixiets/docs since last release333[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Completed step "generateNotes" of plugin "@[secure]/release-notes-generator"334[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"335[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"336[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/changelog" does not provide step "generateNotes"337[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"338[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"339[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/github" does not provide step "generateNotes"340[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"341[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"342[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "[secure]-major-tag" does not provide step "generateNotes"343[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"344[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"345[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins346[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"347[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"348[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins349[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"350[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"351[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins352[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"353[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"354[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins355[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"356[4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]"357[4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins358[4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]"359[4:06:14 PM] [[secure]] › ℹ Start step "prepare" of plugin "@[secure]/changelog"360[4:06:14 PM] [[secure]] [@[secure]/changelog] › ℹ Create /build/release-packages-clone.wcfQ3l/packages/docs/CHANGELOG.md361[4:06:14 PM] [[secure]] › ✔ Completed step "prepare" of plugin "@[secure]/changelog"362[4:06:18 PM] [[secure]] › ✔ Created tag @vanixiets/docs-v0.8.0363[4:06:18 PM] [[secure]] › ℹ Start step "publish" of plugin "@[secure]/github"364[4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Published GitHub release: https://github.com/cameronraysmith/vanixiets/releases/tag/%40vanixiets/docs-v0.8.0365[4:06:19 PM] [[secure]] › ✔ Completed step "publish" of plugin "@[secure]/github"366[4:06:19 PM] [[secure]] › ℹ Start step "success" of plugin "@[secure]/github"367[4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Skip commenting on issues and pull requests.368[4:06:19 PM] [[secure]] [@[secure]/github] › ⚠ DEPRECATION: 'false' for 'successComment' is deprecated and will be removed in a future major version. Use 'successCommentCondition' instead.369[4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Skip closing issue.370[4:06:19 PM] [[secure]] [@[secure]/github] › ⚠ DEPRECATION: 'false' for 'failComment' or 'failTitle' is deprecated and will be removed in a future major version. Use 'failCommentCondition' instead.371[4:06:19 PM] [[secure]] › ✔ Completed step "success" of plugin "@[secure]/github"372[4:06:19 PM] [[secure]] › ℹ Start step "success" of plugin "[secure]-major-tag"373[4:06:19 PM] [[secure]] [[secure]-major-tag] › ℹ Pushing version tag 'docs-v0' to git.374[4:06:19 PM] [[secure]] [[secure]-major-tag] › ℹ Pushing version tag 'docs-v0.8' to git.375To https://github.com/cameronraysmith/vanixiets.git376 * [new tag] docs-v0 -> docs-v0377 * [new tag] docs-v0.8 -> docs-v0.8378[4:06:21 PM] [[secure]] › ✔ Completed step "success" of plugin "[secure]-major-tag"379[4:06:21 PM] [[secure]] › ✔ Published release 0.8.0 on default channel380RELEASE-PACKAGE-OK: packages/docs