Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

chore(tooling): drop MISE_EXPERIMENTAL now that monorepo tasks are stable (mise >= 2026.7.11)

Open
  • Is something wrong?
#891 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, documentation, tooling

Research direction

Start by searching for MISE_EXPERIMENTAL and experimental = true in the six named workflows, root mise.toml, CONTRIBUTING.md, and AGENTS.md; keep the Node.js experimental flag distinct. Review the affected mise tasks, then run mise run build and the security and integration tasks without the setting. Done means the flags and documentation references are removed and the full CI verification passes.

Written by the indexing model from the issue text.

Description

v1
Summary

MISE_EXPERIMENTAL=1 / [settings] experimental = true are set repo-wide to enable monorepo task discovery (mise //cdk:build, etc.). That feature graduated from experimental in mise #10371 (2026-06-13), which predates the repo's new min_version floor of 2026.7.11 (#887/#888). The experimental gate is therefore very likely vestigial and can be removed.

Evidence
  • Monorepo namespaced tasks graduated to stable in jdx/mise#10371 (before 2026.7.11).
  • Empirically: running //cdk:eslint under mise 2026.9.8 with no experimental setting and no MISE_EXPERIMENTAL resolves and executes cleanly.
  • No usage of still-experimental features (mise run --affected, workspace project graph) anywhere in .github/, mise.toml, or scripts/.
Affected places
  • 6 workflows set MISE_EXPERIMENTAL: "1": build.yml, security.yml, security-pr.yml, integ.yml, dead-code-pr.yml, upgrade-main.yml.
  • Root mise.toml: [settings] experimental = true and 8 inline MISE_EXPERIMENTAL=1 mise //… task prefixes (eslint/check/test/security).
  • CONTRIBUTING.md: "Set export MISE_EXPERIMENTAL=1 for namespaced tasks…" and AGENTS.md common-mistakes note.
Do NOT touch (different meaning of "experimental")

node --experimental-strip-types scripts/*.ts in mise.toml — that's a Node.js flag, unrelated to mise's experimental gate.

Acceptance
  • MISE_EXPERIMENTAL / experimental = true removed from configs, workflows, and docs.
  • Full mise run build and the security/integ tasks pass without the flag (the real verification — must run CI, since the root config currently hardcodes it).
Notes

Behavioral change → verify with a full CI run before merge. Deliberately kept out of #888. Needs maintainer approved + assignment before implementation (ADR-003).

Dominant language
TypeScript
Stars
158
Forks
49
Avg merge
3d 16h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/sample-autonomous-cloud-coding-agents

All issues in aws-samples/sample-autonomous-cloud-coding-agents

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.