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

Upgrade to Castle.Core version 4.2.0 #425

Closed
stakx opened this issue Jul 17, 2017 · 3 comments
Closed

Upgrade to Castle.Core version 4.2.0 #425

stakx opened this issue Jul 17, 2017 · 3 comments
Milestone

Comments

@stakx
Copy link
Contributor

stakx commented Jul 17, 2017

This is a reminder to upgrade to the next version of Castle.Core once it's published.

One reason for the upgrade is to solve the package versioning issue discussed in #418 and castleproject/Core#288. Therefore, possibly upgrade in conjunction with #424.

/cc @skovsende, @JohanLarsson

@stakx stakx changed the title Upgrade to Castle.Core version 4.1.2 (or 4.2.0) Upgrade to Castle.Core version 4.2.0 Sep 28, 2017
@stakx
Copy link
Contributor Author

stakx commented Sep 28, 2017

Castle.Core 4.2.0 has just been published (here).

@skovsende
Copy link

Any timeframe on a release?

@stakx
Copy link
Contributor Author

stakx commented Sep 29, 2017

I originally would've liked to include this in 4.8.0, together with the change suggested in #424, but 4.8.0 is probably still many weeks (if not months) away. If it's important for people to have a version of Moq that depends on Castle.Core 4.2.0, then I guess we could do another patch release (4.7.x) sometime during the next 2 weeks or so.

@stakx stakx added this to the v4.7.vNext milestone Sep 29, 2017
@devlooped devlooped locked and limited conversation to collaborators Sep 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants