release: merge develop into release/0.1 for 0.1.0-RC.8 #38

Merged
james.maes merged 3 commits from merge/develop-into-release-0-1-rc8 into release/0.1 2026-11-11 12:36:04 +00:00
Owner

Merges develop (312e95c) into release/0.1 to publish 0.1.0-RC.8.

The only change since 0.1.0-RC.7 is #37:

  • Connect Slack and Install for my organization on the Connections table end on a screen with a Continue to Slack link, one sentence and the link's lifetime, instead of an empty screen.
  • The OAuth callback returns to /app/preferences?section=slack with &result=connected or &error=<code>.
  • An environment without the public URL or the Slack app secrets is refused with a plain message that says which is missing.

The previous release run finished: release/0.1 is at "Bump version to 0.1.0-RC.7 [skip ci]" (2720727), tag v0.1.0-RC.7 exists and its POM is in the registry.

Qualified on this merge commit (a9b84e4) locally: ./mvnw -B verify, 185 tests, 0 Checkstyle violations, guardrails and JaCoCo gate pass. The develop build of 312e95c is green.

🤖 Generated with Claude Code

Merges `develop` (312e95c) into `release/0.1` to publish **0.1.0-RC.8**. The only change since 0.1.0-RC.7 is #37: - Connect Slack and Install for my organization on the Connections table end on a screen with a **Continue to Slack** link, one sentence and the link's lifetime, instead of an empty screen. - The OAuth callback returns to `/app/preferences?section=slack` with `&result=connected` or `&error=<code>`. - An environment without the public URL or the Slack app secrets is refused with a plain message that says which is missing. The previous release run finished: `release/0.1` is at "Bump version to 0.1.0-RC.7 [skip ci]" (2720727), tag `v0.1.0-RC.7` exists and its POM is in the registry. Qualified on this merge commit (a9b84e4) locally: `./mvnw -B verify`, 185 tests, 0 Checkstyle violations, guardrails and JaCoCo gate pass. The `develop` build of 312e95c is green. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 3 commits 2026-11-11 12:34:17 +00:00
fix(connect): a Continue to Slack link, a landing page that exists and a plain refusal
maven / build (push) Successful in 1m35s
build / maven (push) Successful in 1m35s
80bea0f931
Install for my organization and Connect Slack on the Connections table
ended on an empty screen with only a Return button. The screen declared
a view field (authorizeUrl) but no component, and a frontend step shows
only the components it declares. The screen is now an HTML component:
one sentence about what happens, a Continue to Slack link to the consent
page (same tab, so Slack can return the browser) and the lifetime of the
link, read from SlackOAuthState.LIFETIME_SECONDS (10 minutes).

After Slack, the callback redirected to /preferences?section=slack,
which the host UI does not serve. It returns to
/app/preferences?section=slack with &result=connected or &error=<code>.

Connecting in an environment without the public URL or the Slack app
secrets failed with "IllegalArgumentException (Slack public URL is
required)" or "Slack secret unavailable". It is refused before any state
is issued with a user-facing message that says Slack is not set up in
this environment, which of the two is missing, and the names of the
missing environment variables, never a value.

The Preferences action still answers with the authorize address as the
whole message: core has no redirect field on an action result.
qqq-frontend-next opens a message that is only an https address.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
james.maes merged commit d622ad37df into release/0.1 2026-11-11 12:36:04 +00:00
Sign in to join this conversation.