edmand46
a217f255b8
CI / build (push) Successful in 12s
Claude-Session: https://claude.ai/code/session_01SMCvdwDmuxoaqGgvGBLk1V
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
# Changelog
|
|
|
|
## 2.0.0
|
|
|
|
Breaking change — major bump, required by the backend environments release.
|
|
The module path gains the Go major-version suffix: import
|
|
`hub.rudder.build/rudder/rudder-go-sdk/v2` and pull it with
|
|
`go get hub.rudder.build/rudder/rudder-go-sdk/v2@latest`. Nothing else about
|
|
the import changes: the package is still `rudder`.
|
|
|
|
Admin keys are now per environment. A project has exactly two environments,
|
|
`staging` and `prod`, and each has its own Admin Key, so the key you configure
|
|
decides which environment every call reads and writes. There is no environment
|
|
option on the client or on any method, and there is nothing to migrate in code
|
|
— but the key itself changed: the old project Admin Key became the `prod` key
|
|
and a separate `staging` key was generated, both visible under project
|
|
Settings. Players are per environment too, so a player id from one environment
|
|
does not resolve in the other, and the same holds for wallets, inventory,
|
|
storage, counters, quests, runs, battle pass, purchases and leaderboard
|
|
entries.
|
|
|
|
Quests are addressed by slug, because ids differ between staging and prod
|
|
while slugs are stable. `PlayerQuestParameters.QuestID` is now
|
|
`PlayerQuestParameters.QuestSlug`, `PlayerQuestRef` carries `QuestSlug`
|
|
instead of `QuestID`, `PlayerQuest` reports `QuestSlug`, and `Quest`
|
|
(the catalog definition) gained `Slug` alongside its `ID`.
|
|
`Players.VerifyAuth` additionally returns `Environment`, which always matches
|
|
the admin key's environment.
|
|
|
|
Environment create, delete and merge, and project-level admin key
|
|
regeneration, were removed from the platform. This SDK never exposed them, so
|
|
nothing is gone from its surface.
|