Skip to content
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

Closed

Conversation

looker-open-source-automation-bot
Copy link
Collaborator

@looker-open-source-automation-bot looker-open-source-automation-bot commented Mar 17, 2022

🤖 I have created a release *beep* *boop*

sdk-codegen-all: 2.3.0

Features

Bug Fixes

@looker/hackathon: 22.3.0

Features

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/extension-sdk bumped from ^22.2.0 to ^22.2.1
      • @looker/extension-sdk-react bumped from ^22.2.1 to ^22.2.2
      • @looker/extension-utils bumped from ^0.1.6 to ^0.1.7
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
      • @looker/wholly-sheet bumped from ^0.5.25 to ^0.5.26
@looker/sdk: 22.3.0

Features

@looker/sdk-codegen-scripts: 21.3.1

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
      • @looker/sdk-node bumped from ^22.2.0 to ^22.3.0
@looker/sdk-node: 22.3.0

Features

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
looker_sdk: 22.3.0

Features

@looker/extension-sdk: 22.2.1

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
@looker/extension-sdk-react: 22.2.2

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/extension-sdk bumped from ^22.2.0 to ^22.2.1
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
@looker/wholly-sheet: 0.5.26

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
    • devDependencies
      • @looker/sdk-node bumped from ^22.2.0 to ^22.3.0
@looker/extension-utils: 0.1.7

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/extension-sdk bumped from ^22.2.0 to ^22.2.1
      • @looker/extension-sdk-react bumped from ^22.2.1 to ^22.2.2
@looker/run-it: 0.9.30

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/extension-utils bumped from ^0.1.6 to ^0.1.7
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
@looker/api-explorer: 0.9.30

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/extension-utils bumped from ^0.1.6 to ^0.1.7
      • @looker/run-it bumped from ^0.9.29 to ^0.9.30
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0
    • devDependencies
      • @looker/sdk-codegen-scripts bumped from ^21.3.0 to ^21.3.1
      • @looker/sdk-node bumped from ^22.2.0 to ^22.3.0
@looker/extension-api-explorer: 22.2.2

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @looker/api-explorer bumped from ^0.9.29 to ^0.9.30
      • @looker/extension-sdk-react bumped from ^22.2.1 to ^22.2.2
      • @looker/extension-utils bumped from ^0.1.6 to ^0.1.7
      • @looker/run-it bumped from ^0.9.29 to ^0.9.30
      • @looker/sdk bumped from ^22.2.0 to ^22.3.0

This PR was generated with Release Please. See documentation.

Copy link
Contributor

@joeldodge79 joeldodge79 left a 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.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

Copy link
Contributor

@joeldodge79 joeldodge79 left a 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

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions
Copy link
Contributor

Codegen Tests

    1 files    18 suites   29s ⏱️
415 tests 398 ✔️ 14 💤 3 ❌
416 runs  399 ✔️ 14 💤 3 ❌

For more details on these failures, see this check.

Results for commit 41937f6.

@github-actions
Copy link
Contributor

Python Tests

  12 files    12 suites   3m 15s ⏱️
143 tests 143 ✔️ 0 💤 0 ❌
927 runs  927 ✔️ 0 💤 0 ❌

Results for commit 41937f6.

@github-actions
Copy link
Contributor

APIX Tests

    1 files    78 suites   3m 58s ⏱️
313 tests 300 ✔️ 13 💤 0 ❌
329 runs  316 ✔️ 13 💤 0 ❌

Results for commit 41937f6.

@github-actions
Copy link
Contributor

Typescript Tests

    8 files    77 suites   4m 57s ⏱️
169 tests 165 ✔️   4 💤 0 ❌
615 runs  595 ✔️ 20 💤 0 ❌

Results for commit 41937f6.

@jeremytchang
Copy link
Collaborator

Closing. Will use this one instead with 22.4 as top "release-as". #1032

@joeldodge79
Copy link
Contributor

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

@jeremytchang
Copy link
Collaborator

@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.

@joeldodge79
Copy link
Contributor

ah, that's probably because of incompatibilities between the older version we were on and v3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants