chore(release): 0.61.1

[github-actions]

Release-time preparation from merged main. Feature PRs do not carry version or changelog edits.

[tangletools]

✅ Auto-approved PR — 4725c7df

Blanket team auto-approval is intentional. This is not a code review.
No automated review runs on this PR. This approval rests on the rule above alone.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-04T02:28:51Z}

[drewstone]

Summary of changes in this PR (diff base b9af9ea...HEAD)

• Files changed:
  • CHANGELOG.md
  • package.json

Review findings — correctness, security, efficiency, and recommendations

1. CHANGELOG.md

• File: CHANGELOG.md
• Lines changed: 3–5
  • 3: ## 0.61.1
  • 5: - fix(linkedin-ads): expose model-safe targeting arguments
• Observations:
  • The changelog addition is concise and correctly formatted as a new top-level release heading followed by a short bullet describing the fix.
  • No syntax or Markdown formatting issues were introduced.
• Recommendations:
  • For traceability, consider appending the PR/commit reference or author to the changelog entry (e.g. “(PR #351)” or commit hash) so readers can link the release note back to the code change that implemented the fix.
  • If the changelog policy in this repo normally includes longer descriptions or migration notes for behavioral changes, expand this brief note to mention any user-visible effects or upgrade steps (none apparent from this PR alone).

2. package.json

• File: package.json
• Line changed: 3
  • 3: "version": "0.61.1",
• Observations:
  • The only modification in package.json is a version bump from 0.61.0 → 0.61.1 (matches the new CHANGELOG header).
  • No other fields were altered; scripts, dependencies, devDependencies, publishConfig, engines, and packageManager are unchanged.
  • The version bump is consistent with the changelog entry for 0.61.1.
• Security implications:
  • No new dependencies were added or dependency versions modified in this PR. Therefore this PR does not introduce new dependency-related security risk.
  • The repository remains publishable (publishConfig.access = "public"). Nothing in this diff incorrectly exposes secrets or private fields.
• Correctness / Release practices:
  • The package.json bump alone is typical for a release commit. Ensure that the CI/release pipeline actually builds/publishes the compiled artifacts (dist/) and that the published package contains built outputs if the project expects artifacts to be included at publish time.
  • If your publishing workflow requires updating a lockfile (pnpm-lock.yaml) or performing a build before publishing, confirm those steps are performed in CI; this PR makes no lockfile or build output changes.
• Recommendations:
  • If your release process expects a generated changelog entry to include the merge commit or PR number, include that for future traceability.
  • Verify CI has run the prepack/prepublish checks (package.json defines prepack and prepublishOnly scripts) before publishing; the change itself is safe but publishing without running those scripts could produce an incomplete package.

Overall correctness and risk assessment

• The PR only updates metadata: CHANGELOG.md (adds 0.61.1 entry) and package.json (version bump). There are no code changes in this PR that could introduce bugs or regressions.
• No security-sensitive fields were altered; no new dependencies were introduced.
• Main non-code risk is operational: ensure the release pipeline builds and includes compiled artifacts and runs the prepack/prepublish checks referenced in package.json.

Minor suggestions

• Include PR number and/or author in the changelog entry for better traceability (CHANGELOG.md line 5).
• Optionally expand the changelog entry with a one-line description of the effect of “expose model-safe targeting arguments” (what arguments, which adapter behavior changed) so consumers know whether an upgrade is relevant for them.

Conclusion

• This PR is a standard release metadata update (changelog entry + version bump). No code changes were made; no security concerns introduced. Confirm that downstream release steps (build, prepack checks, lockfile handling) are executed by CI/publish tooling as expected.

[tangletools]

✅ Auto-approved PR — e57ab0bf

Blanket team auto-approval is intentional. This is not a code review.
No automated review runs on this PR. This approval rests on the rule above alone.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-04T02:38:50Z}