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

Bump checksync from 4.0.0 to 5.0.4 #778

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 13, 2023

Bumps checksync from 4.0.0 to 5.0.4.

Release notes

Sourced from checksync's releases.

v5.0.4

Patch Changes

  • c7e3562: Fix engines

v5.0.3

Patch Changes

  • 003a91a: Fix rollup config to bundle deps

v5.0.2

Patch Changes

  • 7654f97: Add publishConfig

v5.0.1

Note: There is no v5.0.0. v5 of Checksync uses a new automated publishing setup and that didn't work for the v5.0.0 release. The changes that were in v5.0.0 have been listed below with the v5.0.1 changes.

Major Changes

  • 6b561be: Migrate to TypeScript

    Although there are no functional changes here, we are bumping the major version since changing our static types are provided from Flow to TypeScript could break some folks development setups.

  • 14bbc5f: Working directory updates

    • The location of the configuration file is now used as the current working directory, if a configuration file is used. This means that globs are resolved relative to the configuration file, not the current working directory of the process launching checksync, which makes for a more deterministic behavior for folks trying to define and use their config files.
    • A --cwd argument has been added for specifying the working directory in cases where a configuration file is not used, or the configuration file discover needs to start in a place other than where checksync is invoked. If a configuration file is loaded, the location of that file takes precedence.
  • 95d1a29: Update gitignore support to support full range of syntax. We now use the ignore package to support the gitignore file syntax. New verbose logging has been added to help debug ignore file issues, too.

Patch Changes

  • 9534465: Improved console output to make things easier to read/scan
  • 52ddefd: Updating some things to get automated changeset release working
Changelog

Sourced from checksync's changelog.

5.0.4

Patch Changes

  • c7e3562: Fix engines

5.0.3

Patch Changes

  • 003a91a: Fix rollup config to bundle deps

5.0.2

Patch Changes

  • 7654f97: Add publishConfig

5.0.1

Patch Changes

  • 52ddefd: Updating some things to get automated changeset release working

5.0.0

Major Changes

  • 6b561be: Migrate to TypeScript

    Although there are no functional changes here, we are bumping the major version since changing our static types are provided from Flow to TypeScript could break some folks development setups.

  • 14bbc5f: Working directory updates

    • The location of the configuration file is now used as the current working directory, if a configuration file is used. This means that globs are resolved relative to the configuration file, not the current working directory of the process launching checksync, which makes for a more deterministic behavior for folks trying to define and use their config files.
    • A --cwd argument has been added for specifying the working directory in cases where a configuration file is not used, or the configuration file discover needs to start in a place other than where checksync is invoked. If a configuration file is loaded, the location of that file takes precedence.
  • 95d1a29: Update gitignore support to support full range of syntax. We now use the ignore package to support the gitignore file syntax. New verbose logging has been added to help debug ignore file issues, too.

Patch Changes

  • 9534465: Improved console output to make things easier to read/scan
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 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)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 13, 2023
@changeset-bot
Copy link

changeset-bot bot commented Jun 13, 2023

⚠️ No Changeset found

Latest commit: 9e6e50f

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

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/checksync-5.0.4 branch from 20a2adc to 2bc526b Compare June 13, 2023 00:24
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/checksync-5.0.4 branch from 2bc526b to 1f25243 Compare June 21, 2023 00:10
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/checksync-5.0.4 branch from 1f25243 to 2af676b Compare June 21, 2023 00:12
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/checksync-5.0.4 branch from 2af676b to 0f715af Compare June 27, 2023 00:13
Bumps [checksync](https://github.com/somewhatabstract/checksync) from 4.0.0 to 5.0.4.
- [Release notes](https://github.com/somewhatabstract/checksync/releases)
- [Changelog](https://github.com/somewhatabstract/checksync/blob/main/CHANGELOG.md)
- [Commits](somewhatabstract/checksync@v4.0.0...v5.0.4)

---
updated-dependencies:
- dependency-name: checksync
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/checksync-5.0.4 branch from 0f715af to 9e6e50f Compare June 28, 2023 21:43
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 28, 2023

Looks like checksync is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jun 28, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/checksync-5.0.4 branch June 28, 2023 23:34
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.

0 participants