-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat: recurring scheduled events #10447
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
86a2a6a
to
4fd0f9d
Compare
4fd0f9d
to
cd1533f
Compare
Co-authored-by: Vlad Frangu <[email protected]>
98c0970
to
42b9345
Compare
Why is the status 'blocked'? |
Usually that means the semver status of your PR is higher than what we currently want to release, the blocked label ensure the PR doesn't get merged. For instance, we might currently want a patch (bug fixes only) for our next release, but your PR is minor (features + bug fixes), so we're holding it off. Specifically though, I'm not quite sure what we have planned right now given 14.16.2 was just released yesterday. |
* feat: recurring scheduled events * fix: nullable on patch * docs: remove unnecessary parenthesis Co-authored-by: Vlad Frangu <[email protected]> --------- Co-authored-by: Vlad Frangu <[email protected]>
Please describe the changes this PR makes and why it should be merged:
Upstream:
Depends on:
Status and versioning classification: