-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore: release 15.0.0 #897
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
Conversation
Thanks for the PR! 🚀 |
8016750
to
c121904
Compare
@bharathkkb I have a commit in here, so I'm not comfortable self-LGTMing :) IHAC who is going to need this (ILB subsetting support) in the imminent future -- any ETA to get this released? |
@Jberlinsky Can they reference the release branch for now? In general we avoid rushing releases. |
Absolutely -- just looking for a broad-strokes idea of days/weeks/months to manage expectations :) |
@Jberlinsky we usually aim for 2 weeks, we will need an upgrade guide due to some breaking changes. |
736ee0d
to
692214b
Compare
@bharathkkb Do we need an upgrade guide here? It seems the main breaking change is for ASM and I'm not sure if we actually support upgrade there. |
692214b
to
fba22c0
Compare
@morgante yeah we do not support upgrades for ASM currently, although I do want to resolve #905 to prevent another breaking change. Provider bumps should be no-op but we have historically documented these. |
Yes we should make sure to include that in the release notes (you can simply edit the markdown on this PR). |
7591758
to
919a50b
Compare
919a50b
to
84c7c1a
Compare
🤖 I have created a release *beep* *boop*
15.0.0 (2021-06-08)
⚠ BREAKING CHANGES
enable_l4_ilb_subsetting
flag (feat!: Add support forenable_l4_ilb_subsetting
flag #896)Features
enable_l4_ilb_subsetting
flag (#896) (7531f90)Bug Fixes
ADVANCED_DATAPATH
in more detail (#907) (c32c5d1)This PR was generated with Release Please. See documentation.