Releasing merged features?
See original GitHub issueChore summary
There are several new features/fixes on the develop
branch which didn’t get into 5.8.1 which was released in the meantime. For example these commints:
- https://github.com/stoplightio/spectral/commit/0a8e0a6cbd53018d84352f749ba6ee2b71320498
- https://github.com/stoplightio/spectral/commit/3a5905583ae09f904c66c807e6f175cb9ce6ab04
- https://github.com/stoplightio/spectral/commit/e8c1846c5ea81402d7e79bd4f9e741b95eb46bfb
Tasks
- Create new release with previously unreleased features
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
What is the best way to merge a feature into an older release ...
It seems cherry pick is what you need. With it you can select single commits from another branch and add it to your...
Read more >How to review and merge a big feature
Merging a feature branch into master or dev should be a fast-forward merge, and thus should not require another review.
Read more >Your go-to solution to Merge Feature Release For Free securely
Below, you can find six simple steps to get you started and Merge Feature Release For Free with DocHub: Head to to the...
Read more >Feature Branching: the Key to Faster Releases - Flagship.io
Once a feature branch is completed, tested, and reviewed, it can then be merged back onto the main code base and released to...
Read more >Using a Branching Strategy That Works - Cocoacasts
When every feature and bug fix has been merged into develop , a release branch is created and a release candidate is scheduled...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m hoping to get a major soon. Maintaining v5 is increasingly becoming challenging, because the codebases have diverged notably, and cherry-picking certain changes is not straighforward. If 6.0 does not happen soon, I’ll rewrite the rule for you and get it out in 5.10.
@P0lip regarding 3a59055, we already have a custom rule. We are trying to eliminate our custom rules that duplicate Spectral rules.
If the release after 5.9 is going to be a major version, then I guess we can just wait. But if there is going to be a 5.10, then I would like to submit a PR that makes the change in 3a59055 in a backward compatible way so that it can be included.