This website requires JavaScript.
About
Status
₊˚⊹Discord
Explore
Register
Sign in
Reference in a new issue
Blame
Copy permalink
Reference in a new issue
Copy permalink
TanStack
/
devtools
Star
0
Fork
You've already forked devtools
0
mirror of
https://github.com/TanStack/devtools.git
synced
2026-11-16 10:49:48 +00:00
Code
Issues
Releases
Packages
Activity
@tanstack/devtools-webmcp@0.0.2
devtools
/
pnpm-workspace.yaml
42 lines
1.5 KiB
Raw
Permalink
Normal View
History
ci: update workspace config from other TanStack projects (#182)
2025-09-26 18:27:43 +10:00
security: stricter pnpm config blockExoticSubdeps & trustPolicy (#445)
2026-05-28 21:11:42 +02:00
fix(svelte-devtools): publish compatible adapter exports (#502) * fix(svelte-devtools): publish compatible adapter exports Closes #501 * fix(svelte-devtools): publish Svelte 5 component types * fix(svelte-devtools): package with Svelte tooling * refactor(svelte-devtools): reuse package compiler config * dummy commit * undo dummy commit * test: fix timezone-sensitive date assertion and svelte adapter import Use a local Date so YYYY-MM-DD is stable west of UTC, and import the adapter from its extracted .ts module.
2026-08-20 15:29:28 -04:00
ci: update workspace config from other TanStack projects (#182)
2025-09-26 18:27:43 +10:00
init
2025-07-25 16:40:55 -05:00
ci: update workspace config from other TanStack projects (#182)
2025-09-26 18:27:43 +10:00
test: e2e suite (8 apps + server↔client probe) + unit/component coverage (#472) * test(e2e): scaffold Playwright harness, helper package, react-vite app, shell test-ids * test(e2e): full react-vite shell behavior suite + event-probe * ci(e2e): build packages before running the Playwright suite on every PR * test(e2e): react-start runtime app + server probe * test(e2e): extend event-probe with server-ping emitter + receiver * test(e2e): promote react-start to real server->client via #384 runtime bridge; lock e2e deps * test(e2e): react-nitro runtime app + server probe * test(e2e): cloudflare/workerd runtime app * test(e2e): solid adapter smoke * test(e2e): vue adapter smoke * test(e2e): preact adapter smoke * test(e2e): angular adapter smoke * ci(e2e): run all runtime + adapter e2e apps on every PR; lock e2e deps * test(unit): fill pure-function coverage gaps in devtools + devtools-vite * test(component): Solid shell render + reactivity tests * test(component): React adapter portal wiring test * chore(e2e): formatting and lint fixes * fix(devtools-ui): Checkbox reflects controlled `checked` prop updates * chore(knip): declare doc-script entrypoints and ignore generated intent bin stubs * ci: apply automated fixes * ci(e2e): pin actions to commit SHAs (org policy + zizmor) * test(e2e): make server->client probe deterministic (re-emit until delivered) * ci(e2e): run e2e projects serially — parallel dev servers collide on the shared devtools bus port --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-06-23 20:37:55 +02:00
ci(security): harden CI/CD supply chain and bump pnpm to 11.1.1 (#436) * chore(deps): upgrade pnpm to 11.1.1 Bumps the corepack-managed pnpm version across the root and the four Angular example workspaces. pnpm 11 refuses to run install scripts by default; declare a minimal allowBuilds allowlist in pnpm-workspace.yaml so only the two packages whose postinstalls the build actually needs (esbuild, nx) are permitted. The other eight transitively-pulled postinstalls (sharp, lmdb, workerd, etc.) all fall back to JS paths or are unused during build, and are explicitly denied. Also pin the preinstall guard to only-allow@1.2.2 so it no longer resolves a floating tag from npm on every install. * ci(security): pin actions to SHAs and harden CI/CD supply chain Replaces every mutable workflow reference (@main, @v1, @v3, @v4, @v6.0.2) with a 40-char commit SHA + version comment so Renovate can keep them current. Composite actions in TanStack/config — previously pinned to @main — are the highest-impact change: a force-push or compromised commit there would have given an attacker the npm OIDC publishing identity plus contents/issues/PR write tokens on the next push to main. Other changes in this commit: - release.yml: set cancel-in-progress: false so a re-push cannot abort changesets/action mid-publish and leave partial versions on npm. Add environment: release so required reviewers can be configured in repo settings for an explicit human gate before publish. - triage-agent.yml: add a "SECURITY: Untrusted input" preamble to the Warp agent prompt. The agent reads attacker-controlled issue text, so it must treat that text strictly as data and refuse instructions embedded inside it. Also corrected the bug-report template path (bug-report.yml -> bug_report.yml) that the agent was failing to load. - check-skills.yml / validate-skills.yml: pin @tanstack/intent to a specific version; npm install -g without a version was floating. - pr.yml preview job: pin pkg-pr-new to a specific version; pnpx without a version was floating. - .github/renovate.json: drop :automergeMinor. Combined with floating versions this could have landed a malicious patch without review. - .github/CODEOWNERS (new): require owner review on workflows, package manifests, lockfile, .npmrc, and renovate config. Adjust the owner handle to a team once one exists. - .github/workflows/dependency-review.yml (new): runs actions/dependency-review-action on every PR with fail-on-severity: high to block PRs that introduce known-vulnerable transitive dependencies. * ci(security): bump TanStack/config pin to latest main SHA * fix(ci): correct preinstall skip logic for CI The original `||`-chained preinstall printed "Skipping preinstall..." in CI but then ran only-allow anyway because `process.exit(1)` triggers the `||` operator. CI happened to pass when only-allow was unpinned (npx resolved it differently), but pinning to @1.2.2 forced a fresh registry resolve in which only-allow strictly checks npm_config_user_agent — which, when invoked via npx-inside-pnpm, is npm's, not pnpm's — and rejects. The fix matches the script's stated intent: when CI=true, exit 0 so the `||` does not trigger and only-allow is genuinely skipped. Local installs continue to fall through and enforce pnpm via only-allow as before.
2026-05-12 14:59:09 +02:00