building '/nix/store/hr7kw3j7hr6zcs22a13rk7hpndp2ns51-effect-release-packages-env.drv'... CI-RUN-CONTEXT: branch=main is_main=true RELEASE-CLONE-START: https://github.com/cameronraysmith/vanixiets.git 641ea7a1aebb00276d96a1afc2953321424ef388 RELEASE-PACKAGES-ACTION: release packages discovered: [{"name":"docs","path":"packages/docs"}] RELEASE-PACKAGE-ITERATION: packages/docs running semantic-release in packages/docs... [4:06:06 PM] [[secure]] › ℹ Running [secure] version 25.0.9 [4:06:07 PM] [[secure]] › ✔ Loaded plugin "verifyConditions" from "@[secure]/changelog" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "verifyConditions" from "@[secure]/github" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "prepare" from "@[secure]/changelog" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "publish" from "@[secure]/github" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "addChannel" from "@[secure]/github" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "success" from "@[secure]/github" [4:06:07 PM] [[secure]] › ✔ Loaded plugin "success" from "[secure]-major-tag" [4:06:10 PM] [[secure]] › ✔ Run automated release from branch main on repository https://github.com/cameronraysmith/vanixiets.git [4:06:11 PM] [[secure]] › ✔ Allowed to push to the Git repository [4:06:11 PM] [[secure]] › ℹ Start step "verifyConditions" of plugin "@[secure]/changelog" [4:06:11 PM] [[secure]] › ✔ Completed step "verifyConditions" of plugin "@[secure]/changelog" [4:06:11 PM] [[secure]] › ℹ Start step "verifyConditions" of plugin "@[secure]/github" [4:06:11 PM] [[secure]] [@[secure]/github] › ℹ Verify GitHub authentication [4:06:12 PM] [[secure]] › ✔ Completed step "verifyConditions" of plugin "@[secure]/github" [4:06:12 PM] [[secure]] › ℹ Found git tag @vanixiets/docs-v0.7.0 associated with version 0.7.0 on branch main [4:06:12 PM] [[secure]] › ℹ Found 355 commits since last release [4:06:12 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:12 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Start step "analyzeCommits" of plugin "@[secure]/commit-analyzer" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Found 22 commits for package @vanixiets/docs since last release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(ci): describe the effects registry and the docs-preview check run Change-Id: I64edace62e88789f23958d95fd5881805f636c25 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(ci): describe main-only effects, rehearsals and PR previews Update the contributing, reference and traceability pages, the research notes and the rollup-landing ADR (superseded-in-part notes) for the main-only effect model, and point the path-scope-plugin-releases change at the release-rehearsal check. Change-Id: Ie0d5d0d20bc7e0fc4ab94dc1fd37ca29e42fe973 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(effects): run nixbot effects only on pushes to main Effects held deploy secrets while running pull-request code, and with effects_branches = ["*"] the gitea-mq batch build claimed them first, so main's fast-forward only replayed their statuses: docs were never promoted and nothing was released after 0.7.0. - nixbot.toml: effects_on_pull_requests = false, no effects_branches; PR and batch builds build each effect's dependencies as the required nixbot/effects check - effectRunContext.mainOnlyGuard: skip (exit 0) unless nixbot's id token says push to refs/heads/main; token errors fail - deploy-docs: one path, wrangler deploy of the nix payload, superseded skip, lock; release-packages: one path, superseded skip, lock - onEvent.pull_request.deploy-docs-preview: PR previews from main's code, using the payload nixbot built, with an assets-only config - hermetic release-rehearsal and deploy-docs-rehearsal checks, in the effects' inputs so the pre-merge gate runs the real programs - [secure]: success = {} so [secure]-major-tag runs outside the monorepo wrapper (ADR-0006 floating tags were never made) - nixbot prApproval for OWNER/MEMBER/COLLABORATOR; drop SOPS_AGE_KEY and buildbot wiring from the vanixiets effects secrets - remove preview-version and the legacy deploy-production script Change-Id: I39db5b0c6172dcb0f7e84c92a8983bf482a541ff [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update vitest monorepo to ^5.0.2 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @[secure]/github to ^12.0.10 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update cloudflare-workers-tooling [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency sharp to ^0.35.5 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: Update dependency @types/node to ^26.6.3 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update cloudflare-workers-tooling [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(deps): update astro [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: fix(renovate): group astro with starlight, and regenerate the tree @astrojs/starlight 0.42.2 declares hard peers on astro ^7.2.10 and @astrojs/markdown-remark ^7.3.0. The tree pinned astro 7.2.9 and @astrojs/markdown-remark ^7.2.4, so PR #2913 did not merely conflict, it produced a tree that cannot build: "@astrojs/markdown-remark is too old to render .mdx files ... a ^ range on an older version will not pick it up". Renovate's built-in monorepo preset groups astro with @astrojs/* because they share withastro/astro; starlight lives in withastro/starlight, so it arrives alone, and arriving alone is what breaks the build. The grouping criterion that matters is a shared peer-dependency floor, not a shared upstream repository. The new rule covers astro and @astrojs/**. That pattern takes in @astrojs/cloudflare, which has peers on both astro ^7.2.0 and wrangler ^4.125.0 and therefore straddles this group and cloudflare-workers-tooling. A dependency cannot be in two groups, so the outcome is made deliberate rather than incidental: applyPackageRules iterates packageRules in array order and merges each match over the accumulated config, last match winning for a scalar like groupName (lib/util/package-rules/index.ts), so this rule is placed after the cloudflare rule and the astro group wins. That is the right winner here -- the astro peer floor breaks the build on an ordinary minor bump, whereas the wrangler floor is a caret range any 4.x satisfies. Note that cloudflare-workers-tooling matches only the exact names wrangler and @cloudflare/vite-plugin today, so no dependency actually changes group membership; the ordering guards the case where someone later broadens it. Grouping alone would only relabel the open PRs, so the artifacts are regenerated with `just bun-update-latest-stable`, superseding #2881, #2913 and #2910 with a tree that resolves and builds: @astrojs/cloudflare 14.2.5 -> 14.3.2 @astrojs/markdown-remark ^7.2.4 -> ^7.3.1 @astrojs/starlight 0.41.10 -> 0.42.2 astro 7.2.9 -> 7.3.3 @cloudflare/vite-plugin ^1.54.2 -> ^1.57.0 wrangler ^4.127.1 -> ^4.136.0 One bump was reverted by hand. `bun update --latest` has no knowledge of renovate's holds, so it took conventional-changelog-conventionalcommits from ^9.3.1 to ^10.4.0, straight through the allowedVersions "<10" this config carries because [secure]@25's bundled release-notes-generator cannot resolve conventional-changelog-writer@9. Both package.json files were put back to ^9.3.1 before bun.lock and bun.nix were regenerated. The flake-is-version-ceiling invariant survives: the re-pin phase is load-bearing and `just bun-drift-check` reports "playwright in sync at 1.63.0" afterwards. `just docs-build` completes (84 pages) and `just docs-test` passes 20 unit and 27 e2e tests across chromium, firefox and webkit; the hermetic packages.vanixiets-docs build from the regenerated bun.nix also passes. Change-Id: Ifcd52bda1c1bd2b413c6d77e934e9b2b6a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is patch [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: feat(docs): run firefox and webkit in the hermetic e2e check The linux e2e check ran chromium only, against a browser tree synthesised from nixpkgs chromium rather than the one playwright ships. Both facts rested on one premise: that Chrome-for-Testing binaries crash in the nix build sandbox. A six-arm differential experiment on x86_64-linux DISPROVED that premise - every arm using the Chrome-for-Testing chromium succeeded. The single real sandbox failure was WebKit, which aborts with "Could not create EGL display: no supported platform available" because there is no /dev/dri and playwright-web-flake ships no software EGL vendor. So the nixpkgs-chromium wrapper is removed outright, together with the latent source-build path it dragged in (chromium-unwrapped was in the check's build closure, one cache miss away from compiling chromium from source inside a docs test). Do not reintroduce it: the rationale it was built on is not true. The actual fix is two environment variables pointing libglvnd at mesa's llvmpipe vendor JSON. Coverage is now platform-split, in the project list only; no spec is deleted, skipped, or weakened: x86_64-linux chromium + firefox + webkit 27 passed aarch64-darwin chromium + webkit 18 passed WebKit is net-new coverage on darwin. Firefox is excluded there because it cannot launch inside a darwin nix build - "Failed to launch the browser process / *** You are running in headless mode. / Could not find profile folder." The darwin sandbox (this host builds with sandbox = false), concurrency (reproduced at workers = 1) and HOME (reproduced with a stable /private/tmp HOME) were each ruled out by experiment, and the same firefox binary from the same browsers tree passes outside the build: nix develop -c just docs-test is 27/27 green including all nine firefox specs. The gap is a launch defect of the darwin build environment, not a product defect, and firefox on darwin stays covered by the devShell path. Worker count now follows NIX_BUILD_CORES instead of a fixed 3, with the RAM arithmetic recorded beside it, and playwright.config.ts takes its project and worker selection from PLAYWRIGHT_PROJECTS / PLAYWRIGHT_WORKERS rather than inferring a chromium-only run from CI. Change-Id: I241ce979d6ff2e21cbdeddc96cf6db2d6a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is minor [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: feat(playwright): pin playwright-web-flake to a fork tag at 1.63.0 The playwright-web-flake input was pinned to a fork *branch*, which turned every semantic version bump into an untitled lock-hash bump. `nix flake update` chased the branch head, so the flake-updater bot produced #3097 -- a three-line flake.lock diff that silently carried playwright 1.61.1 -> 1.62.1 with no corresponding npm change and nothing in its title saying a version had moved. Renovate could not catch it either: its regex manager captured currentValue = "fix-webkit-darwin-mac15-arm64", which is not a version, so it never opened a PR for the flake ref at all. The two halves must move together. pkgs/by-name/vanixiets-docs/package.nix materialises PLAYWRIGHT_BROWSERS_PATH directories named from the flake driver's browsers.json revision, while the npm playwright-core resolves them from its own bundled revision. #3097 supplied chromium-1234 to an npm playwright that looked up chromium-1228, and all nine Chromium specs failed to launch in 25 seconds. This change moves both halves at once, and closes the hole that let them separate: flake.nix -> github:cameronraysmith/playwright-web-flake/1.63.0-mac26.2 flake.lock -> dad87258e45f8a4bc606de26438e7e4eb3733bb6 packages/docs -> playwright and @playwright/test 1.63.0, derived from the flake by `just bun-repin-playwright` rather than typed in, so the flake stays the version ceiling bun.lock/bun.nix -> regenerated The tag is 1.63.0-mac26.2, not the earlier -mac26.1: mac26.1 fails to build WebKit on x86_64-linux. autoPatchelfHook hard-errors with auto-patchelf could not satisfy dependency libmanette-0.2.so.0 wanted by .../libWPEWebKit-2.0.so.1.12.0 because playwright-driver/webkit.nix omitted libmanette (the WPE gamepad dependency) from its Linux buildInputs. mac26.2 adds it, and nothing else changes: playwright-driver.version is still exactly 1.63.0, so the npm pins and the browsers.json revisions are untouched and `just bun-drift-check` stays green. Fixing this on the flake side rather than pruning WebKit keeps the Linux devShell -- and any hermetic check that later adopts the full browser set -- able to realise all three browsers from binary substitution. The fork tag is a -mac26. suffix rather than a bare 1.63.0: a bare reuse would shadow upstream's own tag for a different tree and make the eventual fork-drop ambiguous. The suffix sorts after the upstream base under semver and leaves room for patch respins such as this one. It is a tag, not a branch, so the ref no longer moves under the lock. Change-Id: Ie9a818bc08778ddb72994505691ab4616a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The release type for the commit is minor [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update vitest monorepo to v5 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @types/node to ^26.6.2 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update bun to v1.4.2 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency starlight-links-validator to v0.26.0 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: chore(deps): update dependency @biomejs/biome to ^2.5.14 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(tutorials): note the hm-sops-bridge alternative to manual age keys The manual age-key steps remain correct for users a host does not enroll, so they stay; the caveat records that an enrolled user gets the key delivered to /run/secrets/-age-key at mode 0400 with home-manager's sops.age.keyFile already pointed at it, and that assigning that option in a user module on such a host is an evaluation conflict rather than an override. Change-Id: Ic29418c4d29895d49a44ba0a3729e8536a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(sops): drop manual age-key provisioning for bridged NixOS hosts The hm-sops-bridge module exists to eliminate hand-provisioning ~/.config/sops/age/keys.txt on each NixOS host, but the host and user onboarding guides still instructed exactly that step for NixOS, and the user-module example set sops.age.keyFile at ordinary priority, which the bridge's own assignment turns into an evaluation conflict rather than an override. Correct only the NixOS-side occurrences; the darwin steps, the darwin troubleshooting section, the darwin success criteria and the operator-workstation prerequisite are unchanged because darwin keeps the XDG key file. Record next to the bridge what was measured rather than inferred: all six NixOS hosts evaluate sops.useSystemdActivation, services.userborn.enable and systemd.sysusers.enable to false, so the fleet is uniformly in activation-script mode where setupSecrets runs after the users and groups snippets and ordering relative to home-manager is free. srvos's userborn definition is suppressed because every isNormalUser gets autoSubUidGidRange = mkDefault true, which falsifies srvos's mkIf guard. Also record the systemd-mode ordering race that would become possible if the fleet flipped, and that the module has no OpenSpec change and no ADR. Change-Id: I9086324222cf9478566dbc91d11518286a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(omnigent): amend-plan Change-Id: Iba87725b2659d34afc07148ad10863d86a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analyzing commit: docs(openspec): archive pyrite-niri-second-session and sync its spec niri is offered as a second selectable session under GDM, with GNOME still the default and the lockable fallback. Verdict is PASS WITH WARNINGS against an amended requirement. The GNOME-reachability requirement was narrowed after CAM-66 produced an actual counterexample: niri v26.04 has no leader-death lifecycle bridge, so a display-manager restart taken while a niri session is live strands the compositor and blocks the next login. That is upstream behaviour no configuration here supplies, so the requirement was miswritten rather than the implementation deficient. Registration, selectability and default-without-recorded-choice stand unchanged. Warnings carried into the corpus: 8.3-8.5 discharged by evaluation rather than observation; 8.6 declined under CAM-59; 8.2's no-history half is a method limitation, source-read only, because demonstrating it would have destroyed the operator's real session preference. Closes CAM-63. Change-Id: I93baed981453f03d7485a8f998a1efca6a6a6964 [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ The commit should not trigger a release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Analysis of 22 commits complete: minor release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Completed step "analyzeCommits" of plugin "@[secure]/commit-analyzer" [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/release-notes-generator" does not provide step "analyzeCommits" [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/changelog" does not provide step "analyzeCommits" [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/github" does not provide step "analyzeCommits" [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "[secure]-major-tag" does not provide step "analyzeCommits" [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "analyzeCommits" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ The next release version is 0.8.0 [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/commit-analyzer" does not provide step "generateNotes" [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Start step "generateNotes" of plugin "@[secure]/release-notes-generator" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Found 22 commits for package @vanixiets/docs since last release [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Completed step "generateNotes" of plugin "@[secure]/release-notes-generator" [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/changelog" does not provide step "generateNotes" [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "@[secure]/github" does not provide step "generateNotes" [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ Plugin "[secure]-major-tag" does not provide step "generateNotes" [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] [[Function: [secure]-monorepo]] › ℹ No more plugins [4:06:14 PM] [[secure]] › ✔ Completed step "generateNotes" of plugin "[Function: [secure]-monorepo]" [4:06:14 PM] [[secure]] › ℹ Start step "prepare" of plugin "@[secure]/changelog" [4:06:14 PM] [[secure]] [@[secure]/changelog] › ℹ Create /build/release-packages-clone.wcfQ3l/packages/docs/CHANGELOG.md [4:06:14 PM] [[secure]] › ✔ Completed step "prepare" of plugin "@[secure]/changelog" [4:06:18 PM] [[secure]] › ✔ Created tag @vanixiets/docs-v0.8.0 [4:06:18 PM] [[secure]] › ℹ Start step "publish" of plugin "@[secure]/github" [4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Published GitHub release: https://github.com/cameronraysmith/vanixiets/releases/tag/%40vanixiets/docs-v0.8.0 [4:06:19 PM] [[secure]] › ✔ Completed step "publish" of plugin "@[secure]/github" [4:06:19 PM] [[secure]] › ℹ Start step "success" of plugin "@[secure]/github" [4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Skip commenting on issues and pull requests. [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. [4:06:19 PM] [[secure]] [@[secure]/github] › ℹ Skip closing issue. [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. [4:06:19 PM] [[secure]] › ✔ Completed step "success" of plugin "@[secure]/github" [4:06:19 PM] [[secure]] › ℹ Start step "success" of plugin "[secure]-major-tag" [4:06:19 PM] [[secure]] [[secure]-major-tag] › ℹ Pushing version tag 'docs-v0' to git. [4:06:19 PM] [[secure]] [[secure]-major-tag] › ℹ Pushing version tag 'docs-v0.8' to git. To https://github.com/cameronraysmith/vanixiets.git * [new tag] docs-v0 -> docs-v0 * [new tag] docs-v0.8 -> docs-v0.8 [4:06:21 PM] [[secure]] › ✔ Completed step "success" of plugin "[secure]-major-tag" [4:06:21 PM] [[secure]] › ✔ Published release 0.8.0 on default channel RELEASE-PACKAGE-OK: packages/docs