Skip to content

Release v12.142.0 - #803

Merged
jcstorms1 merged 3 commits into
mainfrom
storms/release-new-layer
Jul 29, 2026
Merged

Release v12.142.0#803
jcstorms1 merged 3 commits into
mainfrom
storms/release-new-layer

Conversation

@jcstorms1

@jcstorms1 jcstorms1 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump layer/package version to 12.142.0
  • Adds claude skill for releasing the layer

Includes since last release (v12.141.0):

Test plan

  • Integration test snapshots refreshed against sandbox with updated dd-trace
  • Release Candidate deploy validated (self-monitoring + e2e)

@jcstorms1
jcstorms1 requested review from a team as code owners July 28, 2026 19:01
@jcstorms1
jcstorms1 requested a review from shreyamalpani July 28, 2026 19:01
@jcstorms1 jcstorms1 changed the title v12.142.0 Release v12.142.0 Jul 28, 2026
@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Jul 28, 2026

Copy link
Copy Markdown

Pipelines

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/datadog-lambda-js | e2e-test-status   View in Datadog   GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f62d479 | Docs | Datadog PR Page | Give us feedback!

Comment thread yarn.lock

"@datadog/flagging-core@1.2.1":
version "1.2.1"
resolved "https://registry.npmjs.org/@datadog/flagging-core/-/flagging-core-1.2.1.tgz"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DId dd-trace-js change where they publish to?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this happens when using yarn instead of npm

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that's what happened. They flipped because I ran yarn instead of npm.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as these are equivalent fine by me

(nodeXX)` manual job for every supported runtime. This deploys the
layer to every commercial region.
13. **Guardrail: confirm before triggering**, then run the
`publish-npm-package` manual job. Afterward, verify publicly:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can claude start a manual gitlab job or is this like an instruction for the user

Comment thread .claude/skills/release-lambda-layer/SKILL.md

1. Confirm AWS SSO is set up for both Commercial and GovCloud (see
[cloud-inventory setup](https://github.com/DataDog/cloud-inventory/tree/master/organizations/aws#aws-cli-config-setup--update)).
2. From the Phase 1 pipeline's Sign layer jobs, download each job's

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there might be a signed layer bundle job where you can download all at once

@rithikanarayan rithikanarayan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jcstorms1
jcstorms1 merged commit b6a0581 into main Jul 29, 2026
40 of 42 checks passed
@jcstorms1
jcstorms1 deleted the storms/release-new-layer branch July 29, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants