ci: remove invalid changeset ignore configuration

[ascorbic]

Summary

• Removes the ignore: ["@demo/*"] configuration from .changeset/config.json
• This repository doesn't contain any @demo/* packages, making this configuration invalid and unnecessary

Test plan

• Verify changeset configuration is valid
• Ensure changesets continue to work correctly for the packages in this repository

🤖 Generated with Claude Code

[claude]

PR Review: Remove invalid changeset ignore configuration

Summary

This PR removes the ignore: ["@demo/*"] configuration from .changeset/config.json, changing it to an empty array.

Code Quality ✅

Positive aspects:

• Clean, focused change that addresses a specific configuration issue
• Clear PR description explaining the rationale
• Minimal diff (1 addition, 1 deletion)

Correctness ✅

The change is correct. I verified:

• The repository currently has no demos directory (referenced in CLAUDE.md but not present)
• The only package is vitest-browser-astro (not namespaced with @demo/*)
• Having ignore: ["@demo/*"] would indeed be invalid/unnecessary

Potential Considerations

Minor issue found ⚠️

While reviewing the changeset configuration, I noticed an inconsistency in .changeset/config.json:6:

"repo": "ascorbic/library-template"

This appears to reference a template repository rather than the actual repository (ascorbic/vitest-browser-astro). This should be updated to ensure:

• Changelog links point to the correct repository
• Release notes reference the right GitHub repo

Suggested fix:

"repo": "ascorbic/vitest-browser-astro"

This doesn't block the current PR but should be addressed separately or included if you're already modifying the changeset config.

Test Coverage ✅

The PR description mentions:

• Verify changeset configuration is valid
• Ensure changesets continue to work correctly

These are appropriate test steps for this configuration change. Consider running:

pnpm changeset status

to verify the configuration is valid after the change.

Security & Performance

No security or performance concerns for this configuration change.

Recommendation

LGTM with minor note - The PR is good to merge as-is. However, I recommend creating a follow-up issue or commit to fix the repo field in the changeset config to point to the correct repository.

---

🤖 Review generated with Claude Code