NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
A Lightweight and Powerful Job Scheduling Framework written in Dart. With this framework, you can easily develop a scheduled workflow in Dart.
Last release 4 years ago
no release in 18 months
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 24 of 24 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
24 releases · first in 2022
Added runWorkflow method as an application entry point and deprecated BatchApplication.
runWorkflow method as an application entry point and deprecated BatchApplication. (#180)Eliminated the addSchedule method and added a jobs field to the BatchApplication constructor to specify the ScheduledJobBuilder.
addSchedule method and added a jobs field to the BatchApplication constructor to specify the ScheduledJobBuilder. (#171)argsConfigBuilder callback to BatchApplication to more easily build ArgParser. (#174)addSharedParameter method from BatchApplication and added the sharedParameters argument to the constructor of BatchApplication. (#173)jobParameters argument to the Job and ScheduledJob constructors. (#177)One column per quarter.
Eliminated nextStep when adding steps and added steps to the Job and ScheduledJob constructors. This necessitates a change in the procedure for adding
- Fixed README.md. - Refactored dependencies.
README.md.Made changes to the specifications to make it easier and safer to use the framework.
Task or ParallelTask in the constructor of Step or ParallelStep, not registerStep and registerParallel.branchesOnSucceeded, branchesOnFailed, branchesOnCompleted in the constructors of Events such as Job and Step instead of in the createBranch... methods.BatchApplication has changed. Use the nextSchedule method instead of addJob. Also, pass a class that extends ScheduledJobBuilder to this nextSchedule method; the object that should be returned from ScheduledJobBuilder is ScheduledJob, which must be scheduled.SkipConfiguration and RetryConfiguration settings were limited to Step only. (#145)- Enhanced README.md.
README.md.Enhanced README.md and added examples.
README.md and added examples.The args argument of the onLoadArgs callback is now non-nullable. The null check is no longer necessary.
args argument of the onLoadArgs callback is now non-nullable. The null check is no longer necessary. (#135)Improved names of branch features. Now you can create branches with createBranchOnXXXXX and switch branches with switchBranchToXXXXX.
Allows parallel processing to use the main thread ExecutionContext.
ExecutionContext. (#121)trace, debug, info, warn, error, and fatal from convenient methods of logging feature. Make sure to access the logger from log. (#125Step. Under the new specification, there will always be only one task that can be set in a single step. (#123)Improved schedule checking process.
- Improved README.md.
README.md.Add onRecover feature to RetryConfiguration. It's executed when all retry has failed.
- Enhanced documents on README.
README.Added feature to allow to execute parallel processing. (#25, #74,#84, #87)
parallel processing. (#25, #74,#84, #87)logger_provider. Now you can access to logging features with log.prefix like log.debug('debug'). (#73)MultiLogOutput to allow multiple log output methods. (#82)Added the feature to log notifications at application startup when there are library updates.
info to warn. (#45)SharedParameters. (#13)Improved coloring process for log output. Added logColor field to LogOutput and modified the class ConsoleLogOutput to get the console color.
logColor field to LogOutput and modified the class ConsoleLogOutput to get the console color. (#31)Added the feature to specify any exception type before application execution and skip exceptions that occur during application processing. Only classe
Exception are eligible; classes that inherit from Error are not eligible for this retry feature. (#12)Exception are eligible; classes that inherit from Error are not eligible for this skip feature. (#20)shutdown() to shutdown application in Step (#17).Added onStarted, onSucceeded, onError and onCompleted callbacks for Job, Step and Task.
onStarted, onSucceeded, onError and onCompleted callbacks for Job, Step and Task.LogColor and ConsoleColor.shutdown() to shutdown the application from Task.Precondition as an anonymous function.Added Precondition to check the preconditions for executing Job, Step and Task.
Precondition to check the preconditions for executing Job, Step and Task.Job/Step/Task) based on BranchStatus by using the branchOnSucceeded, branchOnFailed and branchOnCompleted.Job, the schedule argument of the Job object is no longer required. However, be sure to set up a schedule for the root Jobs.Job scheduling. Now you can use CronParser to specify the schedule in Cron format.Added Precondition to check the starting condition of Job and Step. It can be specified as an argument when creating Job and Step instances.
DefaultLogFilter.Precondition to check the starting condition of Job and Step. It can be specified as an argument when creating Job and Step instances.DevelopmentLogFilter and ProductionLogFilter.Added logging feature. Some logs are automatically output to the console during batch processing, but you can output logs at any log level by using th
JobLauncher private and released BatchApplication as new entry point.Wrapped the return value of execute with Future to allow asynchronous processing in Task. Asynchronous processing defined in Task is safely controlled
Future to allow asynchronous processing in Task. Asynchronous processing defined in Task is safely controlled by the batch library, so you don't need to be aware of it when running JobLauncher.- First Release!
Your coding agent can read these notes before it upgrades. Set up the MCP server →