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

When will 4.2.1 be released? #459

Closed
mpszczolinski opened this issue Nov 30, 2022 · 8 comments
Closed

When will 4.2.1 be released? #459

mpszczolinski opened this issue Nov 30, 2022 · 8 comments

Comments

@mpszczolinski
Copy link

Last release (4.2.0) was done in Feb 2022. I see that version 4.2.1 has some useful improvements.

When 4.2.1 will be released? Or did the author abandoned this project?

@IVLIVS-III
Copy link
Contributor

Currently all (old and new) maintainers are short on time, unfortunately.
This PR tracks the new release.

However I cannot give an ETA right now.

@thomassth what is missing until we can finalize the 5.0 pre-release? As far as I can see, only rrule-stuff is missing (#445 / #446 / #448).

@mpszczolinski
Copy link
Author

Thanks IVLIVS-III for the answer.

Howevere you mentioned v.5, which sounds like big improvement. What about 4.2.1 itself?

@IVLIVS-III
Copy link
Contributor

IVLIVS-III commented Nov 30, 2022

@mpszczolinski afaik v4.2.1 was never planned to be released / was never planned to be a standalone version in the first place.

Everything mentioned in the changelog was (prematurely) added to the changelog in this PR (by myself).
At the time of submitting the PR, I did not know what the next planned version number would be, thus listed the changes as a patch.

You could however pin the device_calendar dependency to that specific commit (hash) in your pubspec.yaml until the next version (v5.0) is released to pub.dev.

@thomassth
Copy link
Contributor

I think it's fair to cheerypick commits other than rrule into a 4.2.1 or 4.3

... if someone can do that PR that is

@IVLIVS-III
Copy link
Contributor

@thomassth cherry-picks for 4.3.0 are ready for review on #461. Merging to release automatically published to pub.dev, right?

@thomassth
Copy link
Contributor

oof the cred seems to be expired

need @nickrandolph on that

@nickrandolph
Copy link
Contributor

@thomassth I've updated the secrets. Can you give publishing a go and let me know if there are still issues

@thomassth
Copy link
Contributor

Luckily we got workflow_dispatch for this scenario

No extra commit needed 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants