migrate code from googleapis/nodejs-org-policy #2806
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
kweinmeister
commented
Nov 7, 2022
kweinmeister
commented
- feat!: initial stub of library
- feat: add tests and samples to library
- chore: release 1.0.0
- chore: release 1.0.1 (Add deployment tests. Closes #21. #23)
- chore: release 1.0.2 (Update gcloud-node datastore snippets #31)
- chore: release 1.0.3 (Add webpack sample #38)
- chore: release 1.0.4 (Rename to mongodb and update readme. #43)
- chore: release 1.0.5 (Added sendgrid example app. Also used for Compute Engine snippet. #45)
- chore: release 1.0.6 (Add property query filtering snippet. #47)
- chore: release 1.0.7 (Added Pub/Sub samples. #55)
- chore: release 1.1.0 (Couple of pubsub fixes. #57)
- fix(build): switch primary branch to main (Added Parse-server example. #60)
- chore: release 1.1.1 (Datastore / CloudSQL samples should only store first two octtets of IP #61)
- chore(main): release 1.1.2 (BigQuery samples. #91)
- build!: update library to use Node 12 (Add App Engine error reporting example. #108)
- chore(main): release 2.0.0 (Add Cloud Speech sample. #110)
- chore(main): release 2.0.1 (Switched from JSHint to Semistandard and upgraded dependencies. #116)
- chore(main): release 2.0.2 (Incorrect memcache url in app.yaml #123)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Jeffrey Rennie <rennie@google.com>
🤖 I have created a release \*beep\* \*boop\* --- ### [1.0.4](https://www.github.com/googleapis/nodejs-org-policy/compare/v1.0.3...v1.0.4) (2021-06-30) ### Bug Fixes * **deps:** google-gax v2.17.0 with mTLS ([#41](https://www.github.com/googleapis/nodejs-org-policy/issues/41)) ([e5b7d66](https://www.github.com/googleapis/nodejs-org-policy/commit/e5b7d66e9284bb2f7ac14bb1196fc05f7c7f1bc4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
🤖 I have created a release \*beep\* \*boop\* --- ### [1.0.7](https://www.github.com/googleapis/nodejs-org-policy/compare/v1.0.6...v1.0.7) (2021-08-17) ### Bug Fixes * **deps:** google-gax v2.24.1 ([#54](https://www.github.com/googleapis/nodejs-org-policy/issues/54)) ([a833560](https://www.github.com/googleapis/nodejs-org-policy/commit/a83356087f9ac4e51a031eeb13f536d9f30e2946)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
🤖 I have created a release \*beep\* \*boop\* --- ## [1.1.0](https://www.github.com/googleapis/nodejs-org-policy/compare/v1.0.7...v1.1.0) (2021-08-23) ### Features * turns on self-signed JWT feature flag ([#56](https://www.github.com/googleapis/nodejs-org-policy/issues/56)) ([79c838f](https://www.github.com/googleapis/nodejs-org-policy/commit/79c838f5666f033942c4c2d4b65fac32e074a871)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
*build!: Update library to use Node 12 Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [2.0.1](googleapis/nodejs-org-policy@v2.0.0...v2.0.1) (2022-06-30) ### Bug Fixes * **docs:** describe fallback rest option ([#115](googleapis/nodejs-org-policy#115)) ([c54a19b](googleapis/nodejs-org-policy@c54a19b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
* chore(main): release 2.0.2 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
product-auto-label
bot
added
the
samples
|
Here is the summary of changes. You are about to add 1 region tag.
This comment is generated by snippet-bot.
|
grayside
approved these changes
Nov 8, 2022
.github/workflows/org-policy.yaml
Outdated
| @@ -0,0 +1,67 @@ | |||
| name: orgpolicy | |||
There was a problem hiding this comment.
non-blocking: should we standardize the use of hyphen or no hyphen in org-policy?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.