4 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
max-voitcov	5e9b1ea663	Let a stranded release be re-run without moving the tag ... The v0.2.0 release died twice on the runner -- once OOM-killed by six parallel builds, once with the host going away mid-compile -- and each time the only way back was to delete the tag and push it again. That is destructive, it rewrites published history for a version that may already be half-published, and it is easy to get wrong under pressure. Add a workflow_dispatch trigger so the same release can simply be re-run. goreleaser refuses to release from an untagged commit, so a dispatch can only ever republish a real tag. The sdks job derived VERSION from the ref name, which is the tag on a push but the branch on a dispatch. It now asks git which tag the checked-out commit carries, with --exact-match so an untagged commit fails loudly instead of publishing under the previous version. That needs the tags, hence fetch-depth.	2026-08-26 01:52:53 +03:00
max-voitcov	5b106b406d	Build the release one target at a time so it fits in memory ... The v0.2.0 plugin release ran for 31 minutes and then died: build failed: exit status 1: github.com/pulumi/pulumi/sdk/v3/go/pulumi: compile: signal: killed target=darwin_amd64_v1 `signal: killed` is the OOM killer. A bridged provider links the entire Terraform provider and the Pulumi SDK into a single ~100MB binary, and goreleaser defaults its parallelism to the CPU count, so several of those compiles were resident at once on a runner that could not hold them. Serialise the builds and lower the compiler's GC target. Slower in wall-clock, but it is the difference between a release that finishes and one that does not.	2026-08-26 01:44:19 +03:00
max-voitcov	466e162efe	Keep the schema check honest across a version bump ... The build job regenerates schema.json and diffs it against the checked-in copy, to catch a resources.go edit that never got a `make tfgen`. The comment above it claimed the schema carries no version. It does: tfgen writes the upstream version into `packageDescription`. So the job, which builds at the Makefile's default VERSION, regenerated a schema stamped v0.1.0 and diffed it against the committed v0.2.0 one. The v0.2.0 push failed on a mismatch that had nothing to do with the mapping. Bump the default to match the committed schema and say plainly in both places that the two move together. Verified by running the job's exact command -- `make provider` with no override, then the diff -- which now exits 0. The release job was unaffected: it derives VERSION from the tag.	2026-08-26 01:32:04 +03:00
max-voitcov	73386ba0ff	Bridge what Dokploy v0.30 added, and let the docs through ... Six new resources from terraform-provider-dokploy v0.2.0 -- Network, DnsProvider, VaultProvider, Schedule, VolumeBackup and Libsql -- plus the new properties on Domain (`enabled`), Compose (`serviceNetworks`, `createEnvFile`, `icon`) and Application. Verified with `pulumi up` against a live v0.30.2 instance: create, preview-clean, and destroy. The upstream provider also now refuses a volume Mount with no `volumeName`, which Dokploy would otherwise turn into an anonymous Docker volume recreated on every deploy. That surfaces here at preview time, before anything exists. Two things made that fix nearly invisible to Pulumi users, so this commit fixes the second one: the bridge resolves the upstream `docs/` through the Go module cache, where a locally `replace`d dependency never lands, so tfgen was emitting every resource with no description at all. UpstreamRepoPath now points at the checkout and all 445 inputs carry documentation -- with names rendered per language, so Python readers see `volume_name` where TypeScript readers see `volumeName`.	2026-08-26 00:46:32 +03:00