Repository navigation
v1.1.0
The module path has moved
This repository now lives in the jamf GitHub org, and the module path moved with it:
github.com/jamf/jamfplatform-go-sdk
Update your imports and run go mod tidy:
go get github.com/jamf/jamfplatform-go-sdk@v1.1.0
v1.0.0 under the old Jamf-Concepts path keeps working, so nothing breaks until you upgrade. It will get no further releases.
What's Changed
- chore(security): address the OSS pre-release audit ahead of the jamf org transfer by Neil Martin (@neilmartin83) in #74
- feat(generate): ingest v2154, v2176 and v2192, lift the last two spec holds, and carry preview as a state by Neil Martin (@neilmartin83) in #75
- fix(generate): decode the scalar encoding blueprints' own UI writes by Neil Martin (@neilmartin83) in #76
- build(deps): bump golang.org/x/net from 0.58.0 to 0.59.0 by Dependabot (@dependabot)[bot] in #77
- build(deps): bump golang.org/x/tools from 0.49.0 to 0.50.0 in /tools/generate by Dependabot (@dependabot)[bot] in #78
- chore: repoint the module path at the jamf org by Neil Martin (@neilmartin83) in #79
Highlights
Specs at v2192. Three GitOps builds ingested. Both account holds lifted: the server stopped sending License.type and authZeroRegion, which removed the reason for each. AI Governance declares all twelve operations Preview, so every method's godoc now carries that warning and the GA date.
Blueprints decode the scalars their own UI writes. The Jamf Pro UI stores component configuration numbers as strings, which broke consumers decoding a Component. Field types and request bodies are unchanged, so nothing recompiles.
Deprecation notice. Both /activationcode verbs in proclassic now carry // Deprecated: markers. UpdateActivationCode moves to UpdateActivationCodeV1; GetActivationCode has no successor, because the Pro API publishes no equivalent read. Raised with Jamf. Expect staticcheck SA1019 to flag both until that lands.
Full Changelog: v1.0.0...v1.1.0