Merged
Conversation
…-input [DDW-733] Implement password input component
* [DDW-1227] Introduce a fix for options fixed height * [DDW-1227] Add more optionHeight declarations * [DDW-1227] Fix typo * [DDW-1227] Add GlobalListeners mouse event on root element position * [DDW-1227] Fix flow issues * [DDW-1227] Update CHANGELOG * [DDW-1227] Update stoybook stories due to latest changes * [DDW-1227] CHANGELOG update
* Prepare release 0.9.3
* [DDW-246]: Eliminate usage of deprecated lifecycle methods * [DDW-246]: Restore single quote usage * [DDW-246]: Fix props type in tooltip component
Co-authored-by: Nikola Glumac <niglumac@gmail.com>
* [DDW-733] Refactor jest setup * [DDW-733] Implement advanced password input * [DDW-733] Refactor jest setup * [DDW-733] Implement advanced password input * [DDW-733] Center password input asteriks vertically * [DDW-733] Refine indicator and tooltip styles * [DDW-733] Add theme var for tooltip font-family * [DDW-733] Fix tooltip default font-family Co-authored-by: Nikola Glumac <niglumac@gmail.com>
* [DDW-170] Improve password repeat feature * [DDW-170] Update changelog * [DDW-170] Prepare changelog for vNext * 0.9.4-rc.1 * [DDW-170] Add className prop to password input * 0.9.4-rc.2 * [DDW-170] Fix tooltip regression on hover * 0.9.4-rc.3 * [DDW-170] Fixes show on focus feature * 0.9.4-rc.4 * [DDW-170] Make tooltip border-radius configurable * 0.9.4-rc.5 * [DDW-170] Remove margin from password input * [DDW-170] Fix custom error logic * 0.9.4-rc.6 * [DDW-170] Fix pw input bg colors * 0.9.4-rc.7
…pdate-react-polymorph-and-implement-the-search-style-variables [DDW-645] Update react-polymorph and implement the search style variables
Document new release management
…ub.com:input-output-hk/react-polymorph into feature/ddw-595-improve-input-popover-handling
DominikGuzei
added
release
waiting
…input-popover-handling [DDW-595] Improve input popover handling
Member
Author
|
First release candidate is available as |
…nto release/1.0.0
Contributor
|
@DominikGuzei please proceed with the release. I have merged this so that I can close the JIRA card. |
Member
Author
|
@nikolaglumac i should have added a note here … @daniloprates hasn't merged #179 into the release yet … so this is not included now 😢 but it's ok, I will add this locally and make another release candidate |
Contributor
|
Sorry to cause issues. Let’s be more careful next time... |
Contributor
|
Member
Author
|
@daniloprates my fault, somehow I didn't see your commits - it's all released into 1.0.0 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR prepares the 1.0 release and introduces a new release management process.
🤓 New Release Management
Starting with
1.0.0all future releases will follow semver semantics:patch(eg: 1.0.x) for API compatible bug fixesminor(eg.: 1.x.0) for API compatible new featuresmajor(eg: 2.0.0) for API breaking changesFor early integration of upcoming release changes we use the following conventions:
[current version]-next.xto tag changes for upcoming releases (as we cannot know the necessarysemver for the final release including all the changes).
xin this case is simply a number thatis increased and can be thought of like "slots" for temporary releases
All temporary releases should be published with the
nextnpm dist tag via:npm publish --tag nextso that they are not automatically tagged with the default
latestnpm tag.The
masterbranch only includes commits of final releasesrelease/x.x.xbranches are created as soon as we cut a release and know the correct semver - theyare always targeting the
masterbranch + should be well documented. They can include many releasecandidates which should be tagged like
[next releaes]-rc.Xwhere you increment X per release candidateuntil we are confident that the release is ready to be published under its normal version.
Changes since version 0.9.7
Breaking Changes 💥
Inputnow shows errors on hover and focus by default which can be configured via two new props (PR 173)✨ Features
🐞 Fixes
NumericInputto support DEBUG mode (PR 159)⌛ Potential Changes Waiting for Review