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 dependency publint to ^0.3.0 #5575

Merged
merged 1 commit into from
Jan 7, 2025
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
publint (source) ^0.2.12 -> ^0.3.0 age adoption passing confidence

Release Notes

bluwy/publint (publint)

v0.3.0

Compare Source

Minor Changes
  • The vfs option is removed in favour of an extended support of pack: { tarball: ArrayBuffer | ReadableStream } and pack: { files: PackFile[] } APIs. Now, it is even easier to use publint in the browser or against a packed .tgz file in Node.js. See the docs for more examples of how to use these new options. (#​122)

  • Bump node version support to >=18 (cb2ed8b)

  • publint now runs your project's package manager's pack command to get the list of packed files for linting. The previous npm-packlist dependency is now removed. (#​120)

    A new pack option is added to the node API to allow configuring this. It defaults to 'auto' and will automatically detect your project's package manager using package-manager-detector. See its JSDoc for more information of the option.

    This change is made as package managers have different behaviors for packing files, so running their pack command directly allows for more accurate linting. However, as a result of executing these commands in a child process, it may take 200-500ms longer to lint depending on the package manager used and the project size. The new handling also does not support yarn 1. See this comment for more information.

    If you use yarn 1, you should upgrade to the latest yarn version or a different package manager. Otherwise, no other changes are required for this new behavior.

Patch Changes
  • Initial setup to publish with Changesets (24a62f5)

  • When a dependency with the file: or link: protocol is specified in the package.json, it will now error to prevent accidentally publishing dependencies that will likely not work when installed by end-users (6e6ab33)

  • Fix EXPORT_TYPES_INVALID_FORMAT linting to detect .d.mts and .d.cts files (af5e88b)

  • Updated dependencies [d0b406b]:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from dubzzz as a code owner January 6, 2025 16:18
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 6, 2025
Copy link

changeset-bot bot commented Jan 6, 2025

⚠️ No Changeset found

Latest commit: b96e764

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

pkg-pr-new bot commented Jan 6, 2025

Open in Stackblitz@fast-check/examples

@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@5575

fast-check

npm i https://pkg.pr.new/fast-check@5575

@fast-check/expect-type

npm i https://pkg.pr.new/@fast-check/expect-type@5575

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@5575

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@5575

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@5575

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@5575

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@5575

commit: b96e764

Copy link
Contributor

github-actions bot commented Jan 6, 2025

👋 A preview of the new documentation is available at: http://677c034dae176848fbe80cbd--dubzzz-fast-check.netlify.app

Copy link

codecov bot commented Jan 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.91%. Comparing base (4483a18) to head (b96e764).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5575   +/-   ##
=======================================
  Coverage   94.91%   94.91%           
=======================================
  Files         235      235           
  Lines       10048    10048           
  Branches     2839     2840    +1     
=======================================
  Hits         9537     9537           
  Misses        511      511           
Flag Coverage Δ
unit-tests 94.91% <ø> (ø)
unit-tests-18.x-Linux 94.91% <ø> (ø)
unit-tests-20.x-Linux 94.91% <ø> (ø)
unit-tests-22.x-Linux 94.91% <ø> (ø)
unit-tests-latest-Linux 94.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@dubzzz dubzzz merged commit 8202450 into main Jan 7, 2025
74 checks passed
@dubzzz dubzzz deleted the renovate/publint-0.x branch January 7, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant