You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
src/obp/api-version.ts:33 (drives the dropdown); server/routes/status.ts:141
8
CODE
GLOSSARY_API_VERSION
src/shared-constants.ts:30
'v5.1.0'
src/obp/glossary.ts:37
Group C: default doc version shown in UI
#
Type
Name
Location
Current Value
Purpose
9
ENV
VITE_OBP_API_DEFAULT_RESOURCE_DOC_VERSION
.env:51
commented out
Not set locally — code fallback (#11) is active
10
ENV
VITE_OBP_API_DEFAULT_RESOURCE_DOC_VERSION
.env.example:67
OBPv6.0.0
Template default
11
CODE
OBP_API_DEFAULT_RESOURCE_DOC_VERSION
src/obp/index.ts:34-35
env var ?? 'OBPv7.0.0'
Used in HeaderNav.vue:311, Content.vue:47, Preview.vue:41, SearchNav.vue:84, CollectionView.vue:26, resource-docs.ts:224,237,261,268, router/index.ts:117,144
Group D: plain version-string constants (formerly literals)
Previously hardcoded in obp/... paths. Now backed by simple constants in src/shared-constants.ts that just represent the version string with no semantic meaning.
#1 vs #2 mismatch: local .env is v6.0.0 but template .env.example is v5.1.0. Worth checking that's intentional.
#9 is commented out, so the UI default comes from #11's 'OBPv7.0.0' fallback. That's why localhost:5173 lands on v7.0.0.
#4 (OBP_API_VERSION) is just a re-export of #3 — could be collapsed.
#12 / #13 are deliberately value-named (not purpose-named) so any path can use them without semantic baggage. Bumping a version means updating one constant.