Prepare release 1.0.0 #706
Merged
Conversation
This file contains 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
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
|
Change LGTM, any thoughts on the README file "Running" section? I think we wanted to clearly document the expectations there |
I checked, and the section about hosting your own package registry is in the package-storage README, and it already mentions that is not supported: https://github.com/elastic/package-storage/#host-own-elastic-package-registry |
|
Wel, I will add some "for development" in the package-registry readme 🙂 |
mtojek
approved these changes
Aug 11, 2021
|
🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prepare release 1.0.0. Apart of the version changes, in this PR I also include some additional changes that I would like to see in 1.0: