Repository navigation
deps: Bump @vitest/coverage-v8 from 3.2.4 to 4.1.0 - #1
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.1.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.0/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.0
branch
from
March 23, 2026 12:29
5964a09 to
88dbf1f
Compare
Author
|
Superseded by #10. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.0
branch
March 27, 2026 10:11
AlbSar
pushed a commit
that referenced
this pull request
Apr 14, 2026
…roadmap 6-phase implementation plan for Sprint 138 Architectural Pivot. Coordinator perspective (Alperen + Claude Code executing via Deckent MCP/CLI, native mode). Phase structure: - Phase 0: Pre-flight baseline + source inspection (auditor.ts, file-lock.ts placeholder, tryCodeVerifiedDone location) - Phase 1: DIRECTIVES.md Sprint 138 10-task template (5 CRITICAL + 4 HIGH + 1 NORMAL, Dependencies lines) - Phase 2: Structured plan dry-run (T-005 3rd live dogfood evidence) - Phase 3: Sprint execution (4-wave Phased Hybrid, 3-layer monitoring, meta-dogfood 2x expectation) - Phase 4: Layer 3 verification pipeline (17-criterion sabit + Architectural Pivot Evidence section) - Phase 5: Living record + closing ceremony (FINAL report Section 1+6 inline + Section 20+21 append, 2 commit) - Phase 6: Memory sync + Sprint 139 preflight revised 3 Appendix: - A: DIRECTIVES.md Sprint 138 template pattern - B: Monitoring & Recovery Playbook - C: Success Criteria Hızlı Kontrol (10 checkbox + meta-dogfood 2x) Key verification points: - Meta-dogfood #1: Helper functional upgrade canlı (Task 2 verifyFunctional DONE→TECH_DEBT downgrade) - Meta-dogfood #2: Plan-time collision canlı (Task 5 ↔ Task 6 sprint-finalizer.ts auto-sequentialize) - Meta-dogfood #3 bonus: ADR compliance runtime Execution mode: Deckent Native (MCP + CLI, not subagent dispatch) Clean GO threshold: 8/10 success criteria Target: Layer 3 ≥14/17, readiness ≥4.15, vitest 63 → 0 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
AlbSar
pushed a commit
that referenced
this pull request
May 5, 2026
Two-part fix for Build and Deploy Docs workflow (failing since 2026-04-22):
1. blog-devto-launch.md frontmatter parse error
YAML parser saw `description: ... insight: multi-agent ...` and
interpreted the inner `:` (col 103) as a new mapping key. Wrapped
the value in double quotes so the colon is treated as text.
2. srcExclude config — exclude all internal docs from vitepress build
Comment in config.ts explicitly says "Only guide/ and index.md are
built as user-facing docs," but srcExclude was missing several dirs
that accumulated since Sprint 132+. Added to exclusions:
- audits/** (Sprint 132 W4-customization.md trips Vue compiler
on `obj.#if` interpolation; new Sprint 152 audits would too)
- superpowers/** (sprint-145-implementation-plan.md regex error)
- design/, governance/, sprint-log/, vision/ (internal)
- ROADMAP-GOD-LEVEL.md, KNOWN_ISSUES.md (internal trackers)
Verified locally: `node node_modules/vitepress/bin/vitepress.js build`
→ exit 0, dist/ produced (404.html, guide/, index.html, launch/,
worker-guide.html, vp-icons.css). 3.34s build time.
Note on launch/**: kept INCLUDED (user-facing blog content) — the
fix in #1 means it now parses cleanly.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Bumps @vitest/coverage-v8 from 3.2.4 to 4.1.0.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)94eb73bchore(deps): update eslint packages (#9615)8c96bb0refator: update links to npmx (#9783)aaf7758chore: standardize packages README (#9776)57cbe39chore(deps): updateast-v8-to-istanbulto v1 (#9755)79672d7chore: release v4.1.0-beta.51d9e3b3chore: release v4.1.0-beta.44ff8c6fchore(build): raise build target to the minimum supported, don't bundle utils...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/coverage-v8since your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)