[changelog] [Deprecation Notice] Deprecating currentVersion field in Forge Object Store

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
api, devtools

Research direction

Start by locating the object store shim, the @forge/bridge shim, and the MCP tools forge_objectstore_get and forge_objectstore_list. Compare their GetMetadataResult and ObjectReference metadata with the documented createdAt replacement, then update the affected forge-spec requirement rows and verify currentVersion removal and createdAt population match across the simulated surfaces.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3373
Published: Fri, 31 Jul 2026 05:49:59 GMT
Category: Deprecation Notice
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3373

What's changing

The currentVersion field in the Forge Object Store API is deprecated and will be removed on September 1, 2026. This affects:

  • GetMetadataResult (Custom UI bridge objectStore API)
  • ObjectReference (Object Storage API return value)

Apps should use the createdAt field instead of currentVersion for tracking object versions or timestamps. Updated reference docs:

Parity impact for forge-sim

Simulator areas: object store shim and @forge/bridge shim (Custom UI objectStore surface).

  • If the simulated Object Store returns currentVersion on GetMetadataResult / ObjectReference, that field should be treated as deprecated now and removed to match prod on/after Sep 1, 2026. Apps relying on it in the sim would silently break in real Forge after removal (friendly-success divergence).

  • Verify createdAt is present and correctly populated on both return shapes, since it's the documented replacement.

  • MCP object store tools (forge_objectstore_get / forge_objectstore_list) metadata output should stay consistent with whatever the shims return.

  • forge-spec: update affected requirement rows (behavior change)

Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.