-
Notifications
You must be signed in to change notification settings - Fork 192
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
chore: release main #1026
chore: release main #1026
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
version bumps seem reasonable to me but I'll let someone else double check the versions and changelog entries.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
dc172d8
to
138f672
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need a top-level "release-as": "22.4.0"
key in config
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
138f672
to
41937f6
Compare
Codegen Tests 1 files 18 suites 29s ⏱️ For more details on these failures, see this check. Results for commit 41937f6. |
Python Tests 12 files 12 suites 3m 15s ⏱️ Results for commit 41937f6. |
APIX Tests 1 files 78 suites 3m 58s ⏱️ Results for commit 41937f6. |
Typescript Tests 8 files 77 suites 4m 57s ⏱️ Results for commit 41937f6. |
Closing. Will use this one instead with 22.4 as top "release-as". #1032 |
release-please force pushes the branch each time which updates the PR so in the future there's no need to close a release-PR |
@joeldodge79 For some reason it created a new PR? So I closed this one. Though maybe i messed up somewhere. But yes what you brought up is expected behavior. |
ah, that's probably because of incompatibilities between the older version we were on and v3 |
🤖 I have created a release *beep* *boop*
sdk-codegen-all: 2.3.0
Features
Bug Fixes
@looker/hackathon: 22.3.0
Features
Dependencies
@looker/sdk: 22.3.0
Features
@looker/sdk-codegen-scripts: 21.3.1
Bug Fixes
Dependencies
@looker/sdk-node: 22.3.0
Features
Bug Fixes
Dependencies
looker_sdk: 22.3.0
Features
@looker/extension-sdk: 22.2.1
Dependencies
@looker/extension-sdk-react: 22.2.2
Dependencies
@looker/wholly-sheet: 0.5.26
Dependencies
@looker/extension-utils: 0.1.7
Dependencies
@looker/run-it: 0.9.30
Dependencies
@looker/api-explorer: 0.9.30
Dependencies
@looker/extension-api-explorer: 22.2.2
Dependencies
This PR was generated with Release Please. See documentation.