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

Build(deps): Bump true-myth from 7.4.0 to 8.0.0 #1265

Merged
merged 1 commit into from
Aug 20, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 18, 2024

Bumps true-myth from 7.4.0 to 8.0.0.

Release notes

Sourced from true-myth's releases.

v8.0.0

This is a pretty small “breaking” release: it makes a change so True Myth is more type safe than it was before, specifically when constructing known-Ok or known-Err types with Result.ok and Result.err. In earlier versions, if you wrote Result.ok(123), the type would be Result<number, unknown>. New contributor @​auvred pointed out that in that case, we know there is never an error type, though, so we can use the never type. This is breaking in that you may have to explicitly annotate some types where you did not before, because of the assignability rules for unknown and never (cf. this playground).

Net, very little of your code should have to change, but where it does, it will be safer than it was before! Thanks to @​auvred for the improvement!

💥 Breaking Change

  • #789 fix: set error type in Result.ok and ok type in Result.err to never by default (@​auvred)

🚀 Enhancement

  • #789 fix: set error type in Result.ok and ok type in Result.err to never by default (@​auvred)

📝 Documentation

Committers: 2

Changelog

Sourced from true-myth's changelog.

8.0.0 (2024-08-11)

This is a pretty small “breaking” release: it makes a change so True Myth is more type safe than it was before, specifically when constructing known-Ok or known-Err types with Result.ok and Result.err. In earlier versions, if you wrote Result.ok(123), the type would be Result<number, unknown>. New contributor @​auvred pointed out that in that case, we know there is never an error type, though, so we can use the never type. This is breaking in that you may have to explicitly annotate some types where you did not before, because of the assignability rules for unknown and never (cf. this playground).

Net, very little of your code should have to change, but where it does, it will be safer than it was before! Thanks to @​auvred for the improvement!

💥 Breaking Change

  • #789 fix: set error type in Result.ok and ok type in Result.err to never by default (@​auvred)

🚀 Enhancement

  • #789 fix: set error type in Result.ok and ok type in Result.err to never by default (@​auvred)

📝 Documentation

Committers: 2

Commits
  • 7814d7c Release 8.0.0
  • 5e63694 Merge pull request #789 from auvred/fix/788
  • 0cf1c5d Merge pull request #803 from true-myth/dependabot/npm_and_yarn/types/node-22.1.0
  • 2fee9bb Bump @​types/node from 22.0.3 to 22.1.0
  • 0f7a3d4 Merge pull request #802 from true-myth/dependabot/npm_and_yarn/types/node-22.0.3
  • d8a069f Bump @​types/node from 22.0.2 to 22.0.3
  • 236d862 Merge pull request #800 from true-myth/dependabot/npm_and_yarn/multi-daf8dbcb40
  • 4227aaa Bump vitest and @​vitest/coverage-v8
  • 9ed69b7 Merge pull request #801 from true-myth/dependabot/npm_and_yarn/types/node-22.0.2
  • bf63b9b Bump @​types/node from 22.0.0 to 22.0.2
  • Additional commits viewable in compare view

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 <dependency name> 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)

Bumps [true-myth](https://github.com/true-myth/true-myth) from 7.4.0 to 8.0.0.
- [Release notes](https://github.com/true-myth/true-myth/releases)
- [Changelog](https://github.com/true-myth/true-myth/blob/main/CHANGELOG.md)
- [Commits](true-myth/true-myth@v7.4.0...v8.0.0)

---
updated-dependencies:
- dependency-name: true-myth
  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/true-myth-8.0.0 branch from df5d8d5 to f0f5518 Compare August 18, 2024 12:24
@daanboer daanboer merged commit a54dfa4 into main Aug 20, 2024
7 checks passed
@daanboer daanboer deleted the dependabot/npm_and_yarn/true-myth-8.0.0 branch August 20, 2024 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant