chore(deps): repoint the platform SDK at the jamf org, v1.1.0 - #48
Open
neilmartin83 wants to merge 2 commits into
Open
neilmartin83 wants to merge 2 commits into
neilmartin83 wants to merge 2 commits into
Conversation
The Jamf Platform Go SDK repository moved to the `jamf` GitHub org and the module path moved with it: `github.com/Jamf-Concepts/jamfplatform-go-sdk` becomes `github.com/jamf/jamfplatform-go-sdk`. v1.0.0 is the last release published under the old path, so staying there pins us out of every future release — the same one-way move the Terraform provider made at v0.32.0. Import paths rewritten across `platform/` (client, permissions, app installers, branding images, Jamf Connect, package downloads and their tests) and the requirement bumped v0.23.0 -> v1.1.0, which is where the new path picks up. The intervening releases ingest three GitOps spec builds and fix blueprint scalar decoding; nothing in the generated surface jamformer calls changed shape, so no call sites needed editing. v1.1.0 does mark both `proclassic` /activationcode verbs deprecated — jamformer calls neither. go build, go test ./... and golangci-lint run ./... are clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
neilmartin83
requested review from
hoarek,
jedda-jamf,
leggatron and
shanembrown
as code owners
September 15, 2026 13:22
`github.com/jamf/...` sorts before `github.com/hashicorp/...` where `github.com/Jamf-Concepts/...` sorted after it, so renaming the path in place left two import blocks out of order and the CI gofmt drift check failed. `go fix ./...` reports no further change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The Jamf Platform Go SDK repository moved to the
jamfGitHub org, and the module path moved with it:v1.0.0is the last release published under the old path. It keeps resolving, so nothing breaks by doing nothing — but every future release lands only underjamf, which is the same one-way move the Terraform provider made at v0.32.0.What changed
platform/:client,permissions,appinstallers,brandingimages,jamfconnect,download/packages, and the three tests that name the SDK.golang.org/x/{crypto,mod,net,sync,text}bumps came along withgo mod tidy.No call sites needed editing. The releases in between ingest three GitOps spec builds (specs at v2192, both account holds lifted) and fix blueprint scalar decoding; nothing in the generated surface jamformer calls changed shape.
Notes
Jamf-Concepts/jamfprotect-go-sdkand jamformer's own module path are untouched.proclassic/activationcodeverbs// Deprecated:(staticcheck SA1019). jamformer calls neither, hence the clean lint.Testing
go build✓go vet ./...✓go test ./...✓golangci-lint run ./...-> 0 issues🤖 Generated with Claude Code