chore(deps-dev): bump yeoman-test from 10.1.1 to 11.2.0 in /superset-frontend/packages/generator-superset
User description
Bumps yeoman-test from 10.1.1 to 11.2.0.
Release notes
Sourced from yeoman-test's releases.
v11.2.0
- feat: add support to
@yeoman/adapterv4 (#278) a641abf
https://github.com/yeoman/yeoman-test/compare/v11.1.1...v11.2.0
v11.1.1
- fix: improve createDummyGenerator type (#276) 22abdd7
https://github.com/yeoman/yeoman-test/compare/v11.1.0...v11.1.1
v11.1.0
- feat: change Generator and helpers to protected. (#275) 10b5b68
- fix assertObjectContent for non existing keys (#274) 10ee382
https://github.com/yeoman/yeoman-test/compare/v11.0.0...v11.1.0
v11.0.0
- chore(deps-dev): update yeoman dependencies (#269) 3ae62e3
https://github.com/yeoman/yeoman-test/compare/v11.0.0-0...v11.0.0
v11.0.0-0
- chore!: bump node required to v20 (#267) 781db08
- chore: bump yeoman dependencies (#266) 341d58a
- Bump type-fest from 4.25.0 to 5.0.1 (#265) 95dc975
- chore: types adjusts (#263) db742ae
https://github.com/yeoman/yeoman-test/compare/v10.1.1...v11.0.0-0
Commits
f6b9af111.2.0a641abffeat: add support to@yeoman/adapterv4 (#278)170378111.1.122abdd7fix: improve createDummyGenerator type (#276)c842f9b11.1.010b5b68feat: change Generator and helpers to protected. (#275)10ee382fix assertObjectContent for non existing keys (#274)ce54d8echore(deps-dev): bump the vitest group with 2 updates (#270)9d5488411.0.03ae62e3chore(deps-dev): update yeoman dependencies (#269)- Additional commits viewable in compare view
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)
CodeAnt-AI Description
Update yeoman-test to v11.2.0 for generator tests
What Changed
- The generator-superset package now uses yeoman-test v11.2.0 in devDependencies (replaces v10.1.1), affecting local and CI test runs for the generator.
- Generator tests gain compatibility with newer Yeoman tooling (supports @yeoman/adapter v4) and include fixes that reduce false failures (improved dummy-generator typing and corrected assertion behavior for missing keys).
- No changes to production code or runtime behavior; this only affects developer/test tooling.
Impact
✅ Fewer generator test failures
✅ Support for Yeoman adapter v4 in generator tests
✅ No runtime changes for end users
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
CodeAnt AI is reviewing your PR.
Bito Automatic Review Skipped - Files Excluded
Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at [email protected].
CodeAnt AI finished reviewing your PR.
@dependabot recreate
CodeAnt AI is running Incremental review
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.