chore: release v3.3.14 - #431
Closed
alongubkin wants to merge 2 commits into
Closed
Conversation
Greptile SummaryThe release PR advances the Rust workspace, TypeScript packages, native binding packages, and generated SDK release manifests from 3.3.13 to 3.3.14.
Confidence Score: 4/5The PR is not yet safe to merge because the released platform SDK still identifies default requests as version 3.3.13. The package manifest now publishes @alienplatform/platform-api as 3.3.14, but its generated SDK metadata remains 3.3.13 and the default non-browser request path uses that stale value for the user-agent header. Files Needing Attention: client-sdks/platform/typescript/src/lib/config.ts
|
| Filename | Overview |
|---|---|
| Cargo.toml | Updates the workspace package and internal Rust dependency versions to 3.3.14. |
| Cargo.lock | Synchronizes workspace crate lockfile entries with the 3.3.14 release. |
| client-sdks/platform/typescript/package.json | Advances the platform TypeScript SDK package manifest to 3.3.14. |
| client-sdks/platform/typescript/.speakeasy/gen.yaml | Advances the platform SDK generator release version to 3.3.14. |
| packages/bindings/package.json | Advances the main native bindings wrapper package to 3.3.14 alongside its platform packages. |
Reviews (2): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile
| { | ||
| "name": "@alienplatform/platform-api", | ||
| "version": "3.3.13", | ||
| "version": "3.3.14", |
There was a problem hiding this comment.
When @alienplatform/platform-api 3.3.14 sends a request, its unchanged SDK_METADATA and default user agent still identify the SDK as 3.3.13, causing incorrect version telemetry for the newly published package.
Prompt To Fix With AI
This is a comment left during a code review.
Path: client-sdks/platform/typescript/package.json
Line: 3
Comment:
**Stale platform SDK version metadata**
When `@alienplatform/platform-api` 3.3.14 sends a request, its unchanged `SDK_METADATA` and default user agent still identify the SDK as 3.3.13, causing incorrect version telemetry for the newly published package.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
alongubkin
enabled auto-merge (squash)
August 17, 2026 07:46
Member
Author
|
Closing this release PR for now. We’ll prepare v3.3.14 later from a fresh branch based on current main. |
auto-merge was automatically disabled
August 18, 2026 22:32
Pull request was closed
alongubkin
added a commit
that referenced
this pull request
Aug 21, 2026
## Background Adopted Machines deployments can already have stable customer-owned DNS names and certificates. Treating those deployments as if Alien owns their public hostname produces a second, incorrect URL and can make the control plane manage infrastructure it does not own. ## Changes - add `StackSettings.publicEndpoints` using the existing nested resource/endpoint URL map - preserve every configured URL exactly; do not derive hostnames or synthesize wildcard URLs - document the field as the ownership boundary for adopted Machines endpoints - regenerate the public core schema and Manager OpenAPI/Rust SDK so the map survives deploy CLI → Manager conversion - initialize exhaustive `StackSettings` constructors so all Rust test targets continue to compile Platform PR #431 consumes this field only for Machines deployments, validates complete endpoint ownership against the enabled stack before DNS writes, and excludes those resources from managed DNS/certificate planning. Linear: ALIEN-553 ## Validation - `cargo test -p alien-core machine_public_endpoints_round_trip_without_rewriting_urls --features openapi` - `cargo test -p alien-operator --no-run` - `cargo test -p alien-deploy-cli sdk_stack_settings_preserves_public_endpoints --lib` - `pnpm run generate:manager-rust-sdk` - `pnpm -C packages/core generate` - `pnpm -C packages/core build`
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Version-only release PR generated by the stable release workflow. The Release qualification check builds and records the exact artifact set. After every required check passes and this merges, run the stable publish action from
mainto promote those qualified artifacts.