Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update all non-major dependencies #418

Merged
merged 1 commit into from
Jan 27, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@biomejs/biome (source) 1.5.1 -> 1.5.3 age adoption passing confidence devDependencies patch
@swc/core (source) 1.3.102 -> 1.3.106 age adoption passing confidence devDependencies patch
php 8.3.1 -> 8.3.2 age adoption passing confidence final patch
shivammathur/setup-php 2.28.0 -> 2.29.0 age adoption passing confidence action minor

Release Notes

biomejs/biome (@​biomejs/biome)

v1.5.3

Compare Source

LSP
Bug fixes
  • Fix #​1584. Ensure the LSP only registers the formatter once. Contributed by @​nhedger

  • Fix #​1589. Fix invalid formatting of own line comments when they were at the end of an import/export list. Contributed by @​spanishpear

Configuration
Bug fixes
  • Override correctly the recommended preset (#​1349).

    Previously, if unspecified, Biome turned on the recommended preset in overrides.
    This resulted in reporting diagnostics with a severity level set to off.
    This in turn caused Biome to fail.

    Now Biome won't switch on the recommended preset in overrides unless told to do so.

    Contributed by @​Conaclos

  • Don't format ignored files that are well-known JSONC files when files.ignoreUnknown is enabled (#​1607).

    Previously, Biome always formatted files that are known to be JSONC files (e.g. .eslintrc) when files.ignoreUnknown was enabled.

    Contributed by @​Conaclos

Formatter
Bug fixes
  • Fix #​1178, where the line ending option wasn't correctly applied. Contributed by @​ematipico
  • Fix #​1571. Fix invalid formatting of nested multiline comments. Contributed by @​ah-yu
Linter
Bug fixes
Parser
Bug fixes
  • Accept the const modifier for type parameter in method type signature (#​1624).

    The following code is now correctly parsed:

    type Foo = {
      <const T>();
      method<const T>();
    };

    Contributed by @​magic-akari

  • Correctly parse type arguments in expression(#​1184).

    The following code is now correctly parsed in typescript:

    0 < (0 >= 1);

    Contributed by @​ah-yu

Website
New
Fixes

v1.5.2

Compare Source

CLI
Bug fixes
  • Fix #​1512 by skipping verbose diagnostics from the count. Contributed by @​ematipico

  • Correctly handle cascading include and ignore.

    Previously Biome incorrectly included files that were included at tool level and ignored at global level.
    In the following example, file.js was formatted when it should have been ignored.
    Now, Biome correctly ignores the directory ./src/sub/.

    ❯ tree src
      src
      └── sub
          └── file.js
    
    ❯ cat biome.json
      {
        "files": { "ignore": ["./src/sub/"] },
        "formatter": { "include": ["./src"] }
      }

    Contributed by @​Conaclos

  • Don't emit verbose warnings when a protected file is ignored.

    Some files, such as package.json and tsconfig.json, are protected.
    Biome emits a verbose warning when it encounters a protected file.

    Previously, Biome emitted this verbose warning even if the file was ignored by the configuration.
    Now, it doesn't emit verbose warnings for protected files that are ignored.

    Contributed by @​Conaclos

  • overrides no longer affect which files are ignored. Contributed by @​Conaclos

  • The file biome.json can't be ignored anymore. Contributed by @​ematipico

  • Fix #​1541 where the content of protected files wasn't returned to stdout. Contributed by @​ematipico

  • Don't handle CSS files, the formatter isn't ready yet. Contributed by @​ematipico

Configuration
Bug fixes
  • Fix 1440, a case where extends and overrides weren't correctly emitting the final configuration. Contributed by @​arendjr

  • Correctly handle include when ignore is set (#​1468). Contributed by @​Conaclos

    Previously, Biome ignored include if ignore was set.
    Now, Biome check both include and ignore.
    A file is processed if it is included and not ignored.
    If include is not set all files are considered included.

Formatter
Bug fixes
  • Fix placement of comments before * token in generator methods with decorators. #​1537 Contributed by @​ah-yu

  • Fix #​1406. Ensure comments before the async keyword are placed before it. Contributed by @​ah-yu

  • Fix #​1172. Fix placement of line comment after function expression parentheses, they are now attached to first statement in body. Contributed by @​kalleep

  • Fix #​1511 that made the JavaScript formatter crash. Contributed @​Conaclos

Linter
Enhancements
  • Add an unsafe code fix for noConsoleLog. Contributed by @​vasucp1207

  • useArrowFunction no longer reports function in extends clauses or in a new expression. Contributed by @​Conaclos

    These cases require the presence of a prototype.

  • Add dependency variable names on error message when useExhaustiveDependencies rule shows errors. Contributed by @​mehm8128

Bug fixes
  • The fix of useArrowFunction now adds parentheses around the arrow function in more cases where it is needed (#​1524).

    A function expression doesn't need parentheses in most expressions where it can appear.
    This is not the case with the arrow function.
    We previously added parentheses when the function appears in a call or member expression.
    We now add parentheses in binary-like expressions and other cases where they are needed, hopefully covering all cases.

    Previously:

    - f = f ?? function() {};
    + f = f ?? () => {};

    Now:

    - f = f ?? function() {};
    + f = f ?? (() => {});

    Contributed by @​Conaclos

  • Fix #​1514. Fix autofix suggestion to avoid the syntax error in no_useless_fragments. Contributed by @​togami2864

swc-project/swc (@​swc/core)

v1.3.106

Compare Source

Bug Fixes
Features
Miscellaneous Tasks

v1.3.105

Compare Source

Bug Fixes
Miscellaneous Tasks
Testing

v1.3.104

Compare Source

Bug Fixes

v1.3.103

Compare Source

Bug Fixes
Documentation
Features
  • (html/parser) Allow self-closing /> on non-void HTML elements via a flag (#​8460) (566063d)
Refactor
Testing
shivammathur/setup-php (shivammathur/setup-php)

v2.29.0

Compare Source

Changelog
  • Added support for 'lowest' and 'highest' aliases to specify PHP versions. #​794
    • The lowest alias installs the lowest actively supported version in the PHP project.
    • The 'highest' alias is equivalent to the 'latest' alias, so it installs the latest supported stable PHP version.
- name: Setup PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: lowest # or highest
  • Added support for thread-safe builds on macOS. This completes the support for thread-safe builds on all supported platforms.
- name: Setup ZTS PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: '8.3'
  env:
    phpts: zts
  • Updated documentation for support to read the PHP version from composer.lock and composer.json files.
    • If php-version and php-version-file inputs are not specified, then it can read the php version from platform-overrides.php value in composer.lock or config.platform.php value from composer.json. #​800
- name: Checkout
  uses: actions/checkout@v4
- name: Setup PHP
  uses: shivammathur/setup-php@v2
  • Switched to the new PHPCSStandards/PHP_CodeSniffer repository for builds of phpcs and phpcbf tools. #​809
- name: Setup PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: '8.3'
    tools: phpcs, phpcbf
  • Marked v1 version of the action as completely unsupported, it will receive no updates, please upgrade to v2, if not done already.

  • Fixed installing extensions on Windows for PHP 8.1 by reverting the version bump for minimum stability. #​807

  • Fixed building extensions on PHP 8.4 that used backward compatibility headers from ext/standard to use ext/random/php_random.h header.

  • Improved support for phalcon to install the extension when specified without the version number. #​796

- name: Setup PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: '8.3'
    extensions: phalcon
  • Updated codeql workflow to use v3 versions of codeql actions. #​803

  • Updated docs workflow to use actions/download-artifact@v4 and actions/upload-artifact@v4. #​804, #​805

  • Updated Node.js dependencies.

Merged Pull Requests

For the complete list of changes, please refer to the Full Changelog

Thanks @​dr5hn, @​tighten, @​ZeekInteractive, @​acelaya, and @​fulopattila122 for the sponsorship ❤️

Follow for updates

setup-php reddit setup-php twitter setup-php status


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9c7c5c0 to 75c4088 Compare January 25, 2024 07:28
Copy link

sonarcloud bot commented Jan 27, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@onigoetz onigoetz merged commit beb3f64 into master Jan 27, 2024
10 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch January 27, 2024 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant