Repository navigation
Conversation
…alog keeps only the dataset (#234) Publishing is one call to the LDE backend's POST /v1/triplydb/publish, made with the signed-in author's token. The backend holds the TriplyDB instance, account and token, uploads the TTL and the logos, syncs the service and logs who published. - The Publish dialog asks only for the dataset name; Base URL, Account, API Token and the token reminder are gone. - Test connection checks the dataset through the backend. - The stored config is only { dataset }: an old token in localStorage is removed the first time the editor loads. - The required-services picker gets base URL and account from the backend's publish-target; unconfigured when publishing is not.
Lockfile review✓ No blocking findings. 0 added (0 runtime) · 0 removed (0 runtime) · 65 updated (3 runtime) · 0 downgraded. Updated (65)
|
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://white-sky-02b674303-248.westeurope.1.azurestaticapps.net |
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
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.
Promotes
accto production: v2026.11.0 → v2026.11.1 (#246). 17 commits, 10 non-merge, touching 22 files. The sign-in work (linked-data-explorer#163) already reachedmainthrough #242 without a release cut; v2026.11.1 records it, and this promotion brings what came after.The 10 non-merge commits
85b7f95the bump (chore: bump release to v2026.11.1 #246)e8749d5publish through the LDE backend as the signed-in author; the Publish dialog keeps only the dataset (Publishing has no signed-in user: the TriplyDB token lives in the browser and passes through LDE's open backend #234), with its design, plan and formatting (c70fb42,8ddded4,2601257)49cfbbblock file maintenance (chore(deps): lock file maintenance #196): react and react-dom 19.3.1, lucide-react, 0 downgrades57e995b,2241750,d1a2249: vite 8.3.5, @babel/parser 8.0.10, lucide-react 1.64.0 (chore(deps): update dependency vite to v8.3.5 #231, chore(deps): update dependency @babel/parser to v8.0.10 #236, chore(deps): update dependency lucide-react to v1.64.0 #245)bb71545Node 24.22.2 in.nvmrcand the tooling workflows (chore(deps): update node.js to v24.22.2 #244)ACC state at the release merge (
ab5ff1c, #246)audit,scan,Build and deploy ACC,lockfile-reviewandrelease-sbomgreen.npm testgreen (the human's run),format,lintclean.accandmainfast-forwarded as part of the release.npm run check-previews: OK, every preview belongs to an open pull request.Deploy
The push to
mainrunsazure-static-web-apps-white-sky-02b674303.yml(production).sbom.ymlruns--verify-release;docs/sbom/ttl-editor-2026.11.1.cdx.jsonis committed (8 components, npm 11.19.1) and #246's strict check passed.PROD steps
None in this repository. The production build reads
.env.production:VITE_BACKEND_URL=https://backend.linkeddata.open-regels.nl,VITE_KEYCLOAK_URL=https://keycloak.open-regels.nl. Publishing through the backend needs the LDE backend'sPOST /v1/triplydb/publishon PROD, which went live with linked-data-explorer v2026.11.2 (#339) on 12 November, withTRIPLYDB_ACCOUNTandTRIPLYDB_API_TOKENset there.Behaviour changes that reach PROD
Not in this release
#247 (zizmor-action v0.8.0) opened after the release cut and stays open: its
auditfails until the pin register inSECURITY-PIPELINE.mdrecords the new digest, as for linked-data-explorer #307.