Skip to content
Please note that GitHub no longer supports Internet Explorer.

We recommend upgrading to the latest Microsoft Edge, Google Chrome, or Firefox.

Learn more
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

Release 0.10.0 #133

Merged
merged 156 commits into from Feb 2, 2020
Merged

Release 0.10.0 #133

merged 156 commits into from Feb 2, 2020

Conversation

@FlorianRappl
Copy link
Contributor

FlorianRappl commented Feb 1, 2020

New Pull Request

For more information, see the CONTRIBUTING guide.

Prerequisites

Please make sure you can check the following boxes:

  • I have read the CONTRIBUTING document
  • My code follows the code style of this project
  • All new and existing tests passed

Type(s) of Changes

Contribution Type

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue, please reference the issue id)
  • New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • I have updated the documentation accordingly
  • I have added tests to cover my changes

Description

With 0.10 we get really close to v1. We will now focus on polishing to have a v1 out there that is just fun and efficient to use.

General

For most authors 0.10 should not be breaking. We changed some command line parameters - most of them should not (regularly) be in use. The one that is most prominent is upgrade-pilet. This one now looks upgrade-pilet [version] instead of upgrade-pilet --tag <version>.

🚀 There are multiple new converters out there. All in all most changes are under the hood.

⚠️ Significant changes under the hood

  • We have now piral-base; react-arbiter is gone (piral-base contains the Piral specific part, the React specific part is now fully in piral-core)
  • All plugins do not work against the state container directly, but indirectly via actions (dispatch and readState)
  • The declaration generation works completely different; no longer are api.d.ts files on specific locations required - the whole flow is quite dynamic and should result in elegant and efficient declarations that do not bloat the IDE import section

Remarks

The Piral CLI experiments are not done yet. So potentially there is a 0.11 also incoming before v1. 🌮

Important things first:

Starting with 0.10 we will provide migration guides in case of breaking changes. 🎉 🎉

Otherwise, we'll use the next months to increase test coverage which suffered a bit in the last months. We'll get that up in high numbers again. 👨‍💻

@FlorianRappl FlorianRappl added the release label Feb 1, 2020
@FlorianRappl FlorianRappl added this to the 0.10.0 milestone Feb 1, 2020
@FlorianRappl FlorianRappl self-assigned this Feb 1, 2020
@FlorianRappl FlorianRappl requested a review from lschoett Feb 1, 2020
@FlorianRappl

This comment has been minimized.

Copy link
Contributor Author

FlorianRappl commented Feb 1, 2020

Alright, from my perspective this is a "go". 🤖 🤖 🤖
cc @lschoett

Update (1):
Actually, maybe there is still room for one change. Let me try something!

Update (2):
All done. Ship it!

Copy link
Contributor

lschoett left a comment

Great release with a significant number of extensions and enhancements!

@lschoett lschoett merged commit f5fb8a2 into master Feb 2, 2020
2 checks passed
2 checks passed
license/cla Contributor License Agreement is signed.
Details
piral-CI #888 succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.