Skip to content

ESB-1314 Updated default hub URL - #200

Draft
MEM2677 wants to merge 3 commits into
release/1.2from
ESB-1314
Draft

MEM2677 wants to merge 3 commits into
release/1.2from
ESB-1314

Conversation

@MEM2677

@MEM2677 MEM2677 commented Oct 28, 2026

Copy link
Copy Markdown
Member
  • The default Entando Hub URL changed from https://www.entando.com/entando-hub-api to https://auth.entando.com/entando-hub-api in HubService, the init example, the README and the test mocks.
  • Hub API errors now include the URL that was called and the cause (the HTTP status, or the network error message), not just a generic "Error while contacting the Entando Hub".
  • The Hub API error handler no longer crashes when an error response has an empty body.
  • When entando.json is invalid, the error now points to the right line under Node 20 and later, whose JSON.parse messages show the surrounding source instead of a character position.
  • 7 new tests cover the Node 20 error-message parsing on any Node version, which brings bundle-descriptor-service.ts back above the 90% per-file coverage threshold.
  • lint-staged is pinned to 12.5.0 (was ^13.3.0) so the husky pre-commit hook runs on Node 14, which the project and CI use.
  • The pre-commit hook now runs npx --no-install lint-staged, so it fails clearly if lint-staged isn't installed instead of quietly downloading the latest version.
  • The new .npmrc sets engine-strict=true, so CI's install on Node 14 fails if a future dependency drops Node 14 support.
  • The unused husky v4 "husky": { "hooks": ... } block was removed from package.json.

@MEM2677
MEM2677 requested a review from ffalqui October 28, 2026 11:23
@MEM2677 MEM2677 self-assigned this Oct 28, 2026
@github-actions

Copy link
Copy Markdown

Requested publication of version 1.2.3-SNAPSHOTESB-1314-PR-200

@github-actions

Copy link
Copy Markdown

Requested publication of version 1.2.3-SNAPSHOTESB-1314-PR-200

@github-actions

Copy link
Copy Markdown

Requested publication of version 1.2.3-SNAPSHOTESB-1314-PR-200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants