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 croner 8.1.2 → 9.0.0 (major) #102

Merged
merged 2 commits into from
Nov 24, 2024
Merged

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 24, 2024

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ croner (8.1.2 → 9.0.0) · Repo

Release Notes

9.0.0

Croner 9.0.0

This major release brings significant changes to Croner, improving consistency, fixing bugs, and modernizing the codebase.

Changes

  • Bug Fixes:

    • Fixed an issue where "every X seconds" crons would fail with a "maximum call stack exceeded" error (#260).
    • Fixed an issue where types were not supported when using ES module via jsr.io (#258).
  • API Changes:

    • The new keyword is now mandatory when instantiating Croner (e.g., new Cron(/* ... */)).
    • The default export has been removed. You now need to use import { Cron } from 'croner'; or const { Cron } = require('croner');.
  • File Structure Changes (relevant for direct file access):

    • All files in the /dist directory are now minified. croner.min.js has been renamed to croner.js.
    • Typings have been moved from /types to /dist.
    • Only the /src directory is exposed in the jsr module jsr.io/@hexagon/croner.
  • Codebase Modernization:

    • The entire codebase has been migrated from JavaScript with JSDoc to TypeScript.
    • Deno is now used for formatting, type checking, and linting, resulting in a cleaner and more maintainable repository. Esbuild is used to build the npm module and typings.

Upgrade Notice:

Due to the API and file structure changes, upgrading from 8.x to 9.x may require modifications to your existing code. Please review the above changes carefully before migrating.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 27 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Nov 24, 2024
@depfu depfu bot force-pushed the depfu/update/pnpm/croner-9.0.0 branch from 643fbd7 to 31d5a34 Compare November 24, 2024 11:25
@depfu depfu bot changed the title Update croner 8.1.1 → 9.0.0 (major) Update croner 8.1.2 → 9.0.0 (major) Nov 24, 2024
@depfu depfu bot force-pushed the depfu/update/pnpm/croner-9.0.0 branch from 31d5a34 to f4a92f7 Compare November 24, 2024 11:41
@vaaski vaaski merged commit 4ae5165 into 2024 Nov 24, 2024
1 check passed
@vaaski vaaski deleted the depfu/update/pnpm/croner-9.0.0 branch November 24, 2024 12:08
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