https://docs.all-hands.dev/ logo
Join Slack
Powered by
:thread: to coordinate the next release: - <@U0ASN...
# proj-agent-canvas
a
🧵 to coordinate the next release: • @fierce-account-55183 , you mentioned you could get a list of commits on main that aren't in the release branch, could you post that here? • There are open questions about pinning a version of the extensions repo vs always referring to main • We'll need a release of automations along with agent canvas for some of the fixes going in soon • If you have a mvp fix that needs to go into the next release, please reply to the thread so we can make sure it's cherry-picked in
f
Agent is working on it
q
It might be worth creating a new release branch off the latest main It seems like all the commits going in are MVP related
f
Or just merging main into the rel-1.0.0
Here is the list:
#960 was not part of the MVP - though it is a big enough change I think it should be included
q
Also a just a small NIT, it's helpful to create a new release branch for every release 
rel-1.X.X
It can just be a branch off the prior release branch, but makes it easier to see the various cutoffs without having to inspect the tags
m
feat(frontend): warn when the LLM is not configured after skipping onboarding This pull request is included in v1.0.0-beta.6. However, after installing that version and running it locally, I’m not seeing the expected changes. The image below shows the output I get when running 
npm run dev
from the 
main
branch. Could you help clarify whether I might be missing any additional setup steps or configuration? thankyou
q
I think we're cutting a new release beta.7 that should include everything on main so far, should come through shortly
thankyou 1
Open in Slack
PreviousNext
Powered by