Skip to content

release: 1.2.0-alpha.73#88

Closed
bot-fireworks-ai wants to merge 1 commit into
mainfrom
release-please--branches--main--changes--next
Closed

release: 1.2.0-alpha.73#88
bot-fireworks-ai wants to merge 1 commit into
mainfrom
release-please--branches--main--changes--next

Conversation

@bot-fireworks-ai
Copy link
Copy Markdown
Collaborator

1.2.0-alpha.72 (2026-05-21)

Full Changelog: v1.2.0-alpha.72...v1.2.0-alpha.72

Bug Fixes

  • public-sdk: restore embedding client wiped by 1.2.0-alpha.72 release (#26423) (5a2e407)

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 6db9ad3 to c5d7f13 Compare May 21, 2026 06:18
@Hecate0821 Hecate0821 changed the title release: 1.2.0-alpha.72 release: 1.2.0-alpha.73 May 21, 2026
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from c5d7f13 to ca0ad1b Compare May 21, 2026 06:34
Copy link
Copy Markdown
Collaborator

Per the cleanup sequencing in the Stainless-removal handover, this release PR should not be merged as-is. It still updates .release-please-manifest.json, which #90 deletes, and it is on the old release-please--branches--main--changes--next branch instead of the new autorelease/next flow. After fw-ai/fireworks#26434 and #90 land, close this PR and let the next promote regenerate a clean release PR.

@Hecate0821
Copy link
Copy Markdown
Collaborator

Closing as superseded. PR #90 deletes `.release-please-manifest.json` (which this PR touches), so this would not merge cleanly. The next promote cycle after #90 and fw-ai/fireworks#26434 land will recreate a fresh alpha.73 release PR on the renamed `autorelease/next` branch. The alpha.72 release already carries the embedding fix from fw-ai/fireworks#26423, so nothing user-facing is blocked by this closure.

@Hecate0821 Hecate0821 closed this May 21, 2026
Hecate0821 added a commit that referenced this pull request May 21, 2026
Pulls the generated-code changes (Stainless boilerplate strip across
248 .py files + X-Stainless-* wire-header rename) out of this PR. They
move to a separate follow-up PR.

What stays:

- .github/workflows/release-tag.yml rewritten to read version from
  pyproject.toml [project] (no manifest fallback, no commit-subject
  regex, no workflow_dispatch override). The label-flip step runs
  unconditionally and is a no-op when no PR is associated or the PR is
  not in `autorelease: pending`, so a partial-failure rerun recovers
  cleanly. This is the root-cause fix for the PR #88 stale-title
  incident.
- .github/workflows/release-doctor.yml branch filter switched from
  release-please/ to autorelease/ to match the new bumper.
- .release-please-manifest.json and release-please-config.json deleted
  (the new bumper reads pyproject.toml directly and inlines the
  changelog-sections + extra-files lists).

What is reverted:

- All 248 generated .py files under src/ and tests/ restored to main
  state (Stainless boilerplate header back, X-Stainless-* wire headers
  back).
- {CLAUDE.md, README.md, SECURITY.md, llms.txt, pyproject.toml,
  src/fireworks/lib/.keep, src/fireworks/lib/_legacy_compat.py} restored
  to main.
- .stats.yml restored (Stainless overlay artifact).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Hecate0821 added a commit that referenced this pull request May 21, 2026
* chore: remove Stainless dependencies + fix autorelease single source of truth

This PR completes the de-Stainless migration:

* Strip the "File generated from our OpenAPI spec by Stainless" header
  comment from every auto-generated .py file (248 files).
* Rename wire-protocol HTTP headers: X-Stainless-* -> X-Fireworks-* in
  _base_client.py, _client.py, _constants.py, _utils/_utils.py, and the
  matching test assertions. The X-Fireworks-Lang/-Package-Version/-OS/
  -Arch/-Runtime/-Async/-Retry-Count/-Read-Timeout/-Raw-Response headers
  ship on every request; server-side will be updated to read the new
  prefix.
* Rename internal token "____stainless_override_cast_to" -> "____fireworks_override_cast_to"
  and "stainless-python-retry-..." retry id prefix -> "fireworks-python-retry-...".
* Delete the release-please pipeline artefacts: .release-please-manifest.json,
  release-please-config.json, .stats.yml. The version-bump tool now reads
  pyproject.toml directly as the single source of truth.
* release-tag.yml now reads the version from pyproject.toml on the merged
  commit. No commit-subject regex, no dispatch-input override, no manifest
  fallback. Single source of truth. The "Mark release PR as tagged" step
  also drops its || true masks: a missing PR association or a failed
  label flip is a loud error, not silently swallowed.
* release-doctor.yml branch-name filter switched from "release-please" to
  "autorelease/" prefix; companion PR in staging renames the release PR
  branch to autorelease/next.
* Strip remaining Stainless mentions from README.md, CLAUDE.md, llms.txt,
  pyproject.toml comments, lib/.keep markers, and _legacy_compat.py
  docstring.
* SECURITY.md: drop Stainless contact, consolidate on security@fireworks.ai
  as the sole reporting address for this SDK.

CHANGELOG.md historical entries that reference Stainless are preserved
as-is (history, not current state).

* review: make release-tag.yml label flip recoverable

If "Create tag and GitHub Release" succeeded but "Mark release PR as
tagged" failed (transient API hiccup), the previous structure exited
early on rerun via the `skip=true` path because the tag now existed,
leaving the release PR stuck at `autorelease: pending` forever.

Split the gate: tag existence only skips tag/release creation. The
label-flip step now runs unconditionally and is a no-op when there is
no PR for the commit or the PR is not in `autorelease: pending` state.
A run that just created the tag but cannot find an associated PR still
fails loudly to surface misconfigured release commits.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* scope: revert generated-code touches; keep autorelease SST only

Pulls the generated-code changes (Stainless boilerplate strip across
248 .py files + X-Stainless-* wire-header rename) out of this PR. They
move to a separate follow-up PR.

What stays:

- .github/workflows/release-tag.yml rewritten to read version from
  pyproject.toml [project] (no manifest fallback, no commit-subject
  regex, no workflow_dispatch override). The label-flip step runs
  unconditionally and is a no-op when no PR is associated or the PR is
  not in `autorelease: pending`, so a partial-failure rerun recovers
  cleanly. This is the root-cause fix for the PR #88 stale-title
  incident.
- .github/workflows/release-doctor.yml branch filter switched from
  release-please/ to autorelease/ to match the new bumper.
- .release-please-manifest.json and release-please-config.json deleted
  (the new bumper reads pyproject.toml directly and inlines the
  changelog-sections + extra-files lists).

What is reverted:

- All 248 generated .py files under src/ and tests/ restored to main
  state (Stainless boilerplate header back, X-Stainless-* wire headers
  back).
- {CLAUDE.md, README.md, SECURITY.md, llms.txt, pyproject.toml,
  src/fireworks/lib/.keep, src/fireworks/lib/_legacy_compat.py} restored
  to main.
- .stats.yml restored (Stainless overlay artifact).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

2 participants