search

dev-AshishRanjan / Idea-Arca

Idea Arca (Latin: "Idea Vault") is a Project Idea Bank. Unleash your tech creativity. Discover, collaborate, and bring to life innovative project ideas in various tech fields through this inspirational repository.
https://idea-arca.vercel.app
MIT License
7 stars 9 forks source link

chore(deps)[npm]: bump astro from 2.10.15 to 3.2.2 #17

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps astro from 2.10.15 to 3.2.2.

Release notes

Sourced from astro's releases.

astro@3.2.2

Patch Changes

astro@3.2.1

Patch Changes

@​astrojs/markdown-remark@​3.2.0

Minor Changes

Patch Changes

astro@3.2.0

Minor Changes

  • #8696 2167ffd72 Thanks @​matthewp! - Support adding integrations dynamically

    Astro integrations can now themselves dynamically add and configure additional integrations during set-up. This makes it possible for integration authors to bundle integrations more intelligently for their users.

    In the following example, a custom integration checks whether @astrojs/sitemap is already configured. If not, the integration adds Astro’s sitemap integration, passing any desired configuration options:

    import sitemap from '@astrojs/sitemap';
import type { AstroIntegration } from 'astro';

    const MyIntegration = (): AstroIntegration => {
return {
name: 'my-integration',
    

    'astro:config:setup': ({ config, updateConfig }) => {
  // Look for sitemap in user-configured integrations.
  const userSitemap = config.integrations.find(
    ({ name }) => name === '@astrojs/sitemap'
  );

... (truncated)

Changelog

Sourced from astro's changelog.

3.2.2

Patch Changes

3.2.1

Patch Changes

3.2.0

Minor Changes

  • #8696 2167ffd72 Thanks @​matthewp! - Support adding integrations dynamically

    Astro integrations can now themselves dynamically add and configure additional integrations during set-up. This makes it possible for integration authors to bundle integrations more intelligently for their users.

    In the following example, a custom integration checks whether @astrojs/sitemap is already configured. If not, the integration adds Astro’s sitemap integration, passing any desired configuration options:

    import sitemap from '@astrojs/sitemap';
import type { AstroIntegration } from 'astro';

    const MyIntegration = (): AstroIntegration => {
return {
name: 'my-integration',
    

    'astro:config:setup': ({ config, updateConfig }) => {
  // Look for sitemap in user-configured integrations.
  const userSitemap = config.integrations.find(
    ({ name }) => name === '@astrojs/sitemap'
  );

  if (!userSitemap) {
    // If sitemap wasn’t found, add it.
    updateConfig({
      integrations: [sitemap({ /* opts */ }],
    });
  }
},

    

    };

... (truncated)

Commits
  • 78fda5c [ci] release (#8722)
  • 455af32 Fix CSS styles on windows (#8724)
  • 22fae52 [ci] format
  • 4c2bec6 Fixes View transition styles being missing when component used multiple times...
  • a067c2a [ci] release (#8699)
  • 47ea310 feat: resolve images through the file systems on applicable runtimes (#8698)
  • db83237 refactor(markdown): Move astro:assets-specific code out of the main Vite pl...
  • 148b5b8 Fix preloading stylesheets in view transitions (#8707)
  • 3458081 Fix duplicated Astro and Vite injected styles (#8706)
  • 31c59ad Fix hydration on slow connection (#8680)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
vercel[bot] commented 11 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
idea-arca ❌ Failed (Inspect) Oct 2, 2023 7:10pm
pr-explainer-bot[bot] commented 11 months ago

Pull Request Report

Greetings!

Hey there! I'm your friendly neighborhood GitHub bot, here to provide you with a report on the changes made in the pull request. Let's dive right in, shall we?

Changes

  1. Bumped the astro dependency from version 2.10.14 to 3.2.2.

Suggestions

No suggestions provided.

Bugs

No bugs reported.

Improvements

No improvements suggested.

Rating

I'll rate the code based on three criteria: readability, performance, and security. Here's my brief assessment:

That's it for the report! If you have any further questions or need assistance, feel free to reach out. Happy coding!

vizipi[bot] commented 11 months ago

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments.

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

Committed file ranks

  • 86.36%[package-lock.json]
  • 86.36%[package.json]
    • pull-request-quantifier-deprecated[bot] commented 11 months ago

    This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

    Quantification details

    ``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

    Why proper sizing of changes matters

    Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

    Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

    dependabot[bot] commented 11 months ago

    Superseded by #24.