chore: repoint the module path at the jamf org - #79
Merged
Merged
Conversation
The repository has been transferred from `Jamf-Concepts` to `jamf`, so the module path moves with it: `github.com/jamf/jamfplatform-go-sdk`. This is the breaking half of the transfer and it is deliberately a separate step, as it was for `terraform-provider-jamfplatform`. The transfer alone leaves every consumer building, because GitHub redirects the old path and `proxy.golang.org` has the cached zips; renaming the module is what forces each consumer to rewrite its imports. The substitution is one-for-one and nothing else moved: - the three module declarations (root, `tools`, `tools/generate`) - `tools/generate/config.json`'s `module` key, which is where every generated import line comes from, plus its test - the generated tree, via `make generate` — `api/*.json` produced a zero diff, so no published spec is touched - `client.go`, the acceptance suite and the handwritten unit tests - `README.md`, `CONTRIBUTING.md`, `CLAUDE.md` `go build`, `go vet` on all three modules and on `-tags acceptance`, `make test` and `make lint` all pass. Three consumers import the old path and will need migrating once a release is tagged here: `jamf/terraform-provider-jamfplatform`, `Jamf-Concepts/jamf-cli` and `Jamf-Concepts/jamformer`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Neil Martin (neilmartin83)
deployed
to
acceptance
September 15, 2026 11:25 — with 
GitHub Actions
Active
GitHub Actions
Active
Neil Martin (neilmartin83)
deployed
to
acceptance
September 15, 2026 11:25 — with
GitHub Actions
Active
GitHub Actions
Active
Neil Martin (neilmartin83)
deployed
to
acceptance
September 15, 2026 11:25 — with
GitHub Actions
Active
GitHub Actions
Active
Neil Martin (neilmartin83)
deployed
to
acceptance
September 15, 2026 11:25 — with
GitHub Actions
Active
GitHub Actions
Active
Neil Martin (neilmartin83)
deployed
to
acceptance
September 15, 2026 11:25 — with
GitHub Actions
Active
GitHub Actions
Active
Neil Martin (neilmartin83)
enabled auto-merge
September 15, 2026 11:37
Daniel MacLaughlin (daniel-maclaughlin)
self-requested a review
September 15, 2026 12:04
Daniel MacLaughlin (daniel-maclaughlin)
approved these changes
Sep 15, 2026
This branch was successfully deployed
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
2 participants
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 repository has been transferred from
Jamf-Conceptstojamf, so the module path moves with it:github.com/jamf/jamfplatform-go-sdk.This is the breaking half of the transfer, and it is deliberately a separate commit from the transfer itself — the same order
terraform-provider-jamfplatformtook. The transfer alone leaves every consumer building, because GitHub redirects the old path andproxy.golang.orgserves the cached zips. Renaming the module is what forces each consumer to rewrite its imports.What moved
The substitution is one-for-one and nothing else changed.
go.mod,tools/go.mod,tools/generate/go.modtools/generate/config.json's"module"key — the single source of every generated import line — plusvalidate_test.gomake generate;api/*.jsonproduced a zero diff, so no published spec is touchedjamfplatform/client.go, the acceptance suite, the unit testsREADME.md,CONTRIBUTING.md,CLAUDE.md241 files, 342 insertions, 342 deletions.
Verification
go build ./...go vet ./...on all three modules, plusgo vet -tags acceptance ./jamfplatform/— the suite is build-tagged, somake testcannot compile itmake test— green, every packagemake lint— 0 issues, including the taggederrcheck/ineffassignrowgit fetchagainst the new remoteNo acceptance run: this change cannot alter a request, a URL or a payload.
Downstream
Three consumers import the old path and each needs its imports rewritten once a release is tagged here. Reported, not migrated from this repository:
jamf/terraform-provider-jamfplatform(v1.0.0)Jamf-Concepts/jamf-cli(v1.0.0)Jamf-Concepts/jamformer(v0.23.0)One reference is deliberately left alone:
jamfplatform/acc_proclassic_profile_payloads_test.go:855citesJamf-Concepts/terraform-jamf-platform#488, a different repository that has not moved.🤖 Generated with Claude Code