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
6 stars 8 forks source link

chore(deps)[npm]: bump astro from 2.10.15 to 4.2.1 #71

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps astro from 2.10.15 to 4.2.1.

Release notes

Sourced from astro's releases.

astro@4.2.1

Patch Changes

astro@4.2.0

Minor Changes

  • #9566 165cfc154be477337037185c32b308616d1ed6fa Thanks @​OliverSpeir! - Allows remark plugins to pass options specifying how images in .md files will be optimized

  • #9661 d6edc7540864cf5d294d7b881eb886a3804f6d05 Thanks @​ematipico! - Adds new helper functions for adapter developers.

    • Astro.clientAddress can now be passed directly to the app.render() method.
    const response = await app.render(request, { clientAddress: '012.123.23.3' });
    • Helper functions for converting Node.js HTTP request and response objects to web-compatible Request and Response objects are now provided as static methods on the NodeApp class.
    http.createServer((nodeReq, nodeRes) => {
  const request: Request = NodeApp.createRequest(nodeReq);
  const response = await app.render(request);
  await NodeApp.writeResponse(response, nodeRes);
});
    • Cookies added via Astro.cookies.set() can now be automatically added to the Response object by passing the addCookieHeader option to app.render().
    -const response = await app.render(request)
-const setCookieHeaders: Array<string> = Array.from(app.setCookieHeaders(webResponse));

    -if (setCookieHeaders.length) {
    

      

    • for (const setCookieHeader of setCookieHeaders) {
      • 

    • 

         headers.append('set-cookie', setCookieHeader);

      

      • 

    • }
-}
+const response = await app.render(request, { addCookieHeader: true })

  • #9638 f1a61268061b8834f39a9b38bca043ae41caed04 Thanks @​ematipico! - Adds a new i18n.routing config option redirectToDefaultLocale to disable automatic redirects of the root URL (/) to the default locale when prefixDefaultLocale: true is set.

    In projects where every route, including the default locale, is prefixed with /[locale]/ path, this property allows you to control whether or not src/pages/index.astro should automatically redirect your site visitors from / to /[defaultLocale].

    You can now opt out of this automatic redirection by setting redirectToDefaultLocale: false:

    // astro.config.mjs

    • ... (truncated)

    Changelog

    Sourced from astro's changelog.

    4.2.1

    Patch Changes

    4.2.0

    Minor Changes

    • #9566 165cfc154be477337037185c32b308616d1ed6fa Thanks @​OliverSpeir! - Allows remark plugins to pass options specifying how images in .md files will be optimized

    • #9661 d6edc7540864cf5d294d7b881eb886a3804f6d05 Thanks @​ematipico! - Adds new helper functions for adapter developers.

      • Astro.clientAddress can now be passed directly to the app.render() method.
      const response = await app.render(request, { clientAddress: '012.123.23.3' });
      • Helper functions for converting Node.js HTTP request and response objects to web-compatible Request and Response objects are now provided as static methods on the NodeApp class.
      http.createServer((nodeReq, nodeRes) => {
  const request: Request = NodeApp.createRequest(nodeReq);
  const response = await app.render(request);
  await NodeApp.writeResponse(response, nodeRes);
});
      • Cookies added via Astro.cookies.set() can now be automatically added to the Response object by passing the addCookieHeader option to app.render().
      -const response = await app.render(request)
-const setCookieHeaders: Array<string> = Array.from(app.setCookieHeaders(webResponse));

      -if (setCookieHeaders.length) {
      

        

      • for (const setCookieHeader of setCookieHeaders) {
        • 

      • 

           headers.append('set-cookie', setCookieHeader);

        

        • 

      • }
-}
+const response = await app.render(request, { addCookieHeader: true })

  • #9638 f1a61268061b8834f39a9b38bca043ae41caed04 Thanks @​ematipico! - Adds a new i18n.routing config option redirectToDefaultLocale to disable automatic redirects of the root URL (/) to the default locale when prefixDefaultLocale: true is set.

    In projects where every route, including the default locale, is prefixed with /[locale]/ path, this property allows you to control whether or not src/pages/index.astro should automatically redirect your site visitors from / to /[defaultLocale].

    You can now opt out of this automatic redirection by setting redirectToDefaultLocale: false:

    • ... (truncated)

    Commits


    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 6 months ago

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

    Name Status Preview Comments Updated (UTC)
    idea-arca ❌ Failed (Inspect) Jan 22, 2024 7:47pm
    git-greetings[bot] commented 6 months ago

    Thanks @dependabot[bot] for opening this PR!

    For COLLABORATOR only :

    git-greetings[bot] commented 6 months ago
    PR Details of @dependabot[bot] in Idea-Arca : OPEN CLOSED TOTAL
    6 24 30
    pr-explainer-bot[bot] commented 6 months ago

    Pull Request Report

    Hey there! 👋 Here's a report on the changes made in the pull request:

    Changes

    1. Bumped the astro dependency from version 2.10.14 to 4.2.1. 🚀

    Suggestions

    No suggestions provided. Skipping this section. 😉

    Bugs

    No bugs reported. Skipping this section. 🐛

    Improvements

    No improvements mentioned. Skipping this section. 🛠️

    Rating

    Rate the code from 0 to 10 based on the following criteria:

    Please provide a brief explanation for the rating.

    vizipi[bot] commented 6 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

  • 95.45%[package.json]
  • 97.73%[package-lock.json]
    • pull-request-quantifier-deprecated[bot] commented 6 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 6 months ago

    Superseded by #72.