chore(deps-dev): bump astro-vtbot from 1.10.6 to 2.0.3

[dependabot]

Bumps astro-vtbot from 1.10.6 to 2.0.3.

Changelog

Sourced from astro-vtbot's changelog.

2.0.3 - 2025-01-02

Patch Changes

• 428d815: <InspectionChamber /> and <CamShaft />: Added a workaround to handle quoted animation names in Webkit which caused user agent animation names not being recognized in Safari.

2.0.2 - 2025-01-01

Patch Changes

• 70a8fba: Applies bug fixes from dependencies for <ElementCrossing /> and <CamShaft />.

2.0.1 - 2024-12-31

Patch Changes

• 8ec2ee2: Fixes links and typos in README

2.0.0 - 2024-12-30

Major Changes

• 85e6fb4: When installed as an integration, the and components will no longer be auto-installed on all pages. The autoLint and loadingIndicator options in the vtbot() integration in your astro-config file now default to false instead of true. These options will be completely removed in a future release.

  What's Changing?

  • If you use astro-vtbot as a library and haven't installed it as an Astro integration: Nothing changes for you.
  • If you have installed it as an integration and have explicitly opted out of the linter and loading indicator: remove these settings: {autoLint: false, loadingIndicator: false} from your astro-config file.
  • If you have installed it as an integration and called vtbot({...}) with one option or no parameter at all: To ensure continued functionality, explicitly add the <Linter /> and/or <LoadingIndicator /> components to the pages that need them. Ideally, include them in your common layout.astro file for consistency across your site. Make sure that the call to vtbot() in you astro-config file does not set any options.

  Temporary Workaround

  You can restore the previous behavior by enabling the deprecated options, but note that they will be removed soon:

  import vtbot from 'astro-vtbot';
  export default defineConfig({
  integrations: [
  vtbot({
  autoLint: true,
  loadingIndicator: true,
  }),
  ],
  });

  Take action now to ensure smooth transitions and avoid future disruptions.

... (truncated)

Commits

• See full diff 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cloudflare-workers-and-pages]

Deploying fullstackpanama with    Cloudflare Pages

Latest commit:	a8eb87f
Status:	✅  Deploy successful!
Preview URL:	https://52dc5199.fullstackpanama.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-astr-7y0w.fullstackpanama.pages.dev

View logs

[dependabot]

Superseded by #39.