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

chore(deps): update external major (major) #539

Merged
merged 4 commits into from
Mar 25, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github 9.2.6 -> 10.0.2 age adoption passing confidence
@​types/github-slugger 1.3.0 -> 2.0.0 age adoption passing confidence
@types/node (source) 18.19.26 -> 20.11.30 age adoption passing confidence
c8 8.0.1 -> 9.1.0 age adoption passing confidence
husky 8.0.3 -> 9.0.11 age adoption passing confidence
lint-staged 14.0.1 -> 15.2.2 age adoption passing confidence
remark-gfm ^3.0.0 -> ^4.0.0 age adoption passing confidence
remark-parse (source) 10.0.2 -> 11.0.0 age adoption passing confidence
remark-stringify (source) 10.0.3 -> 11.0.0 age adoption passing confidence
semantic-release 21.1.2 -> 22.0.12 age adoption passing confidence
unified (source) 10.1.2 -> 11.0.4 age adoption passing confidence

Release Notes

semantic-release/github (@​semantic-release/github)

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported
bcoe/c8 (c8)

v9.1.0

Compare Source

Features
Bug Fixes
  • refactor: remove stale check for createDynamicModule (5e18365)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • build: minimum Node.js version is now 14.14.0
Features
  • build: minimum Node.js version is now 14.14.0 (2cdc86b)
  • deps: update foreground-child to promise API (#​512) (b46b640)
  • deps: use Node.js built in rm (2cdc86b)
typicode/husky (husky)

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

  • Enhanced security with CI and npm --provenance for safer publishing.
  • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
  • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
  • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
  • Modified behavior when .git is missing; it now triggers a warning instead of failure.
  • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
  • Updated the Husky API for module usage.
  • Transitioned to ESM for module usage.
  • Dropped support for Node 14 and 16.
  • Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test
okonet/lint-staged (lint-staged)

v15.2.2

Compare Source

Patch Changes
  • #​1391 fdcdad4 Thanks @​iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

v15.2.1

Compare Source

Patch Changes
  • #​1387 e4023f6 Thanks @​iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.

v15.2.0

Compare Source

Minor Changes
  • #​1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.
Patch Changes
  • #​1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #​1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #​1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #​1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Compare Source

Minor Changes
Patch Changes

v15.0.2

Compare Source

Patch Changes
  • #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes
  • #​1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Compare Source

Major Changes
  • #​1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This release drops support for Node.js 16, which is EOL after 2023-09-11.
    Please upgrade your Node.js to the latest version.

    Additionally, all dependencies have been updated to their latest versions.

remarkjs/remark-gfm (remark-gfm)

v4.0.0

Compare Source

Change
  • b8cc334 Update @types/mdast, unified, utilities
    migrate: update too
  • 9eb0f54 Change to use exports
    migrate: don’t use private APIs
  • 5715c93 Change to require Node.js 16
    migrate: update too

Full Changelog: remarkjs/remark-gfm@3.0.1...4.0.0

remarkjs/remark (remark-parse)

v11.0.0

Compare Source

(see 15.0.0)

semantic-release/semantic-release (semantic-release)

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.
unifiedjs/unified (unified)

v11.0.4

Compare Source

Types

Full Changelog: unifiedjs/unified@11.0.3...11.0.4

v11.0.3

Compare Source

Fix
  • 8dee2ab Fix support for functions in data

Full Changelog: unifiedjs/unified@11.0.2...11.0.3

v11.0.2

Compare Source

  • cea788b Fix type of settings if nothing is registered yet

Full Changelog: unifiedjs/unified@11.0.1...11.0.2

v11.0.1

Compare Source

  • d1a915d Fix incorrect type of settings in presets

Full Changelog: unifiedjs/unified@11.0.0...11.0.1

v11.0.0

Compare Source

Change
  • baf80b2 Change to require Node.js 16
    migrate: update too
  • dd9834a Update @types/unist
    migrate: update too
  • 620ccf9 Update vfile
    migrate: update too
Change (unlikey to affect you)
  • a44db46 Add Data, Settings types to augment shared data
    migrate: if you deal with data, type it, see commit for info
  • fb49556 Change to replace Buffer with Uint8Array
    migrate: you’re probably fine unless you use weird encodings, see commit for details if so
  • f3e71a8 Remove Attacher type
    migrate: use Plugin instead
  • cc53bb6 Remove FrozenProcessor type
    migrate: use Processor instead
  • 1aa3494 Change to yield undefined, not null
    migrate: expect undefined
  • 932c140 Change to use exports
    migrate: don’t use private APIs
  • 8e57478 Remove support for classes as compilers, parsers
    migrate: if you love classes, see commit message
  • 4676814 Remove support for compilers returning nullish
    migrate: nobody did that
  • 807ffb9 Add improved types
    migrate: it’s probably just better if anything changed at all
  • b35afe0 Add useful error on empty presets
    by @​wooorm in https://github.com/unifiedjs/unified/pull/202
  • 6f068a0 Fix to deep clone preset settings
  • 56ee288 Fix non-first parameter merging when reconfiguring plugins
Misc

Full Changelog: unifiedjs/unified@10.1.2...11.0.0


Configuration

📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@github-actions
Copy link

github-actions bot commented Sep 18, 2023

This PR will trigger no release when merged.

@renovate renovate bot force-pushed the renovate-major-external-major branch 5 times, most recently from 4e1c997 to 5dfe905 Compare September 25, 2023 16:24
@renovate renovate bot force-pushed the renovate-major-external-major branch from 5dfe905 to 74bbec3 Compare September 30, 2023 15:05
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from a627fe3 to 34f3c93 Compare October 14, 2023 16:00
@renovate renovate bot force-pushed the renovate-major-external-major branch from 34f3c93 to bf7a3c2 Compare October 14, 2023 19:05
@renovate renovate bot changed the title fix(deps): update external major (major) chore(deps): update external major (major) Oct 14, 2023
@renovate renovate bot force-pushed the renovate-major-external-major branch 3 times, most recently from bb6e0cc to a9556df Compare October 21, 2023 15:19
@renovate renovate bot force-pushed the renovate-major-external-major branch 7 times, most recently from 5f33bd3 to 39aa7ad Compare October 28, 2023 19:54
@renovate renovate bot force-pushed the renovate-major-external-major branch 4 times, most recently from f1b9718 to 634f330 Compare November 4, 2023 19:43
@renovate renovate bot force-pushed the renovate-major-external-major branch 3 times, most recently from 23f3f9f to b16f135 Compare November 13, 2023 09:49
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 563a42c to 125ab5a Compare November 17, 2023 04:49
@renovate renovate bot force-pushed the renovate-major-external-major branch 5 times, most recently from 9069cf2 to 852b79b Compare March 2, 2024 19:23
@renovate renovate bot force-pushed the renovate-major-external-major branch 4 times, most recently from ea6732a to a0ba585 Compare March 13, 2024 17:02
@renovate renovate bot force-pushed the renovate-major-external-major branch 7 times, most recently from 33f2071 to 1ded6cc Compare March 20, 2024 16:01
@renovate renovate bot force-pushed the renovate-major-external-major branch 3 times, most recently from b1e583a to 39471e1 Compare March 25, 2024 11:23
@renovate renovate bot force-pushed the renovate-major-external-major branch from 39471e1 to feb1008 Compare March 25, 2024 11:28
Copy link
Contributor Author

renovate bot commented Mar 25, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

Copy link

codecov bot commented Mar 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.75%. Comparing base (3b74f4f) to head (b20cdd1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #539   +/-   ##
=======================================
  Coverage   99.75%   99.75%           
=======================================
  Files          11       11           
  Lines        2039     2039           
=======================================
  Hits         2034     2034           
  Misses          5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tripodsan tripodsan merged commit 51be972 into main Mar 25, 2024
8 checks passed
@tripodsan tripodsan deleted the renovate-major-external-major branch March 25, 2024 12:24
@tripodsan
Copy link
Collaborator

🎉 This PR is included in version 8.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant