Skip to content
This repository was archived by the owner on Mar 11, 2026. It is now read-only.

chore: release 9.4.0#1092

Merged
freelerobot merged 2 commits intomasterfrom
release-v9.4.0
Jun 14, 2021
Merged

chore: release 9.4.0#1092
freelerobot merged 2 commits intomasterfrom
release-v9.4.0

Conversation

@release-please
Copy link
Copy Markdown
Contributor

@release-please release-please bot commented Jun 9, 2021

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

9.4.0 (2021-06-11)

Features

  • detect Google and W3C trace context (including in middleware) (#1088) (864f188)
  • users can log raw http request objects with trace (#1086) (19b943e)

Bug Fixes


This PR was generated with Release Please. See documentation.

@release-please release-please bot requested review from a team June 9, 2021 10:15
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 9, 2021
@product-auto-label product-auto-label bot added the api: logging Issues related to the googleapis/nodejs-logging API. label Jun 9, 2021
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jun 9, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 9, 2021
@freelerobot freelerobot added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jun 9, 2021
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 10, 2021
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Jun 10, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 10, 2021
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Jun 10, 2021
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 11, 2021
@snippet-bot
Copy link
Copy Markdown

snippet-bot bot commented Jun 11, 2021

No region tags are edited in this PR.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Jun 11, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 11, 2021
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Jun 11, 2021
@freelerobot freelerobot removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jun 14, 2021
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 14, 2021
@yoshi-kokoro yoshi-kokoro removed kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Jun 14, 2021
@freelerobot freelerobot merged commit 1eb1086 into master Jun 14, 2021
@freelerobot freelerobot deleted the release-v9.4.0 branch June 14, 2021 02:59
@yoshi-automation
Copy link
Copy Markdown
Contributor

@release-tool-publish-reporter
Copy link
Copy Markdown

The release build has started, the log can be viewed here. 🌻

@release-tool-publish-reporter
Copy link
Copy Markdown

🥚 You hatched a release! The release build finished successfully! 💜

gcf-merge-on-green bot pushed a commit to googleapis/nodejs-logging-winston that referenced this pull request Jun 14, 2021
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
GautamSharda pushed a commit to googleapis/google-cloud-node that referenced this pull request Jan 14, 2026
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
GautamSharda pushed a commit to googleapis/google-cloud-node that referenced this pull request Jan 20, 2026
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
GautamSharda pushed a commit to googleapis/google-cloud-node that referenced this pull request Jan 21, 2026
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
GautamSharda pushed a commit to googleapis/google-cloud-node that referenced this pull request Feb 2, 2026
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
GautamSharda pushed a commit to googleapis/google-cloud-node that referenced this pull request Feb 3, 2026
Fixes #597  🦕

Blocked: [Nodejs-logging release](googleapis/nodejs-logging#1092)

Changes: 
- Users can now hardcode a spanId via `LOGGING_SPAN_KEY` when using Winston
- Middleware scenario: if span is detected from the request obj, it is propagated to makeChildLogger, and emitRequestLog capabilities, and span is included in the final child logs.
- Fix e2e tests given `originalUrl` needs to be a real url
- export function `getCurrentTraceFromAgent`
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: logging Issues related to the googleapis/nodejs-logging API. autorelease: published cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants