-
Notifications
You must be signed in to change notification settings - Fork 339
DISCUSS - 0.17.0
Release
#2176
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
Comments
potential blockers:
Less urgent but worth considering:
I think next release should be 0.17.0, the scrollspy and search-as-you-type changes are big ones. |
You are right, I agree this would be more like ⛔ Blockers:
We should look into this (cc @gabalafou @peytondmurray). I was not counting this feature in the upcoming release due to this comment from @gabalafou
ref: #2119 (comment) But since it is merged now, we should look into fixing the issues. Tracking in #2178 🐛 Non-blockers, but would be nice to look into:
I looked at the fail you mentioned in another PR, which seems new. I will see if I can reproduce it. However, I re-ran the workflow and the |
By the way, I think #2185 fixes the blocking scroll spy issues |
We still have some small tweaks I need to make to our CI. I started them but have been swamped these past weeks, I will prioritise that next week so we can move towards a new release. |
It has been over three months since our last release, and a good number of enhancements and bug fixes have been added since then. I believe we are in a good place to think about making a new release.
Also, having a new release should help fix #2088
I also want to get #2159 in this upcoming release, as the current version breaks some stuff for downstream projects.
cc/ @gabalafou @drammock
The text was updated successfully, but these errors were encountered: