Skip to content

Conversation

@authentik-automation
Copy link
Contributor

Cherry-pick of #18950 to version-2025.12 branch.

Original PR: #18950
Original Author: @kensternberg-authentik
Cherry-picked commit: 47aa68f

@netlify
Copy link

netlify bot commented Jan 21, 2026

Deploy Preview for authentik-integrations ready!

Name Link
🔨 Latest commit 2ed5c70
🔍 Latest deploy log https://app.netlify.com/projects/authentik-integrations/deploys/697230d049e6510008102639
😎 Deploy Preview https://deploy-preview-19638--authentik-integrations.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@codecov
Copy link

codecov bot commented Jan 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.41%. Comparing base (b4f7455) to head (2ed5c70).
⚠️ Report is 4 commits behind head on version-2025.12.
✅ All tests successful. No failed tests found.

❗ There is a different number of reports uploaded between BASE (b4f7455) and HEAD (2ed5c70). Click for more details.

HEAD has 6 uploads less than BASE
Flag BASE (b4f7455) HEAD (2ed5c70)
integration 1 0
unit 9 5
unit-migrate 4 3
Additional details and impacted files
@@                 Coverage Diff                 @@
##           version-2025.12   #19638      +/-   ##
===================================================
- Coverage            92.92%   86.41%   -6.52%     
===================================================
  Files                  946      946              
  Lines                52288    52288              
===================================================
- Hits                 48589    45183    -3406     
- Misses                3699     7105    +3406     
Flag Coverage Δ
e2e 43.48% <ø> (+0.73%) ⬆️
integration ?
unit 73.91% <ø> (-17.65%) ⬇️
unit-migrate 78.99% <ø> (-1.76%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@GirlBossRush GirlBossRush force-pushed the cherry-pick/18950-to-version-2025.12 branch from 9d7a6aa to d324e4c Compare January 22, 2026 00:29
@github-actions
Copy link
Contributor

authentik PR Installation instructions

Instructions for docker-compose

Add the following block to your .env file:

AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-d324e4c977b63db4705928683943d0ffe00f7800
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s

Afterwards, run the upgrade commands from the latest release notes.

Instructions for Kubernetes

Add the following block to your values.yml file:

authentik:
    outposts:
        container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
    image:
        repository: ghcr.io/goauthentik/dev-server
        tag: gh-d324e4c977b63db4705928683943d0ffe00f7800

Afterwards, run the upgrade commands from the latest release notes.

* web: Add InvalidationFlow to Radius Provider dialogues

## What

- Bugfix: adds the InvalidationFlow to the Radius Provider dialogues
  - Repairs: `{"invalidation_flow":["This field is required."]}` message, which was *not* propagated
    to the Notification.
- Nitpick: Pretties `?foo=${true}` expressions: `s/\?([^=]+)=\$\{true\}/\1/`

## Note

Yes, I know I'm going to have to do more magic when we harmonize the forms, and no, I didn't add the
Property Mappings to the wizard, and yes, I know I'm going to have pain with the *new* version of
the wizard. But this is a serious bug; you can't make Radius servers with *either* of the current
dialogues at the moment.

* This (temporary) change is needed to prevent the unit tests from failing.

\# What

\# Why

\# How

\# Designs

\# Test Steps

\# Other Notes

* Revert "This (temporary) change is needed to prevent the unit tests from failing."

This reverts commit dddde09.

* website: fix bad escaping of URLs in release notes

## What

Fixes bad escaping of URLs in the release notes that resulted in mangled output.

v2024.6.4 had entries that looked like this:

```
##### `GET` /providers/google_workspace/{#123;id}#125;/
```

v2025.4.md had entries that looked like this:

```
##### `GET` /policies/unique_password/{#125;#123;policy_uuid}/
```

A couple of straightforward search-and-replaces has fixed the issue.

## Notes

Two of the release notes had bad escaping of URLs. I'm not sure how the error was made or got past,
but it was obvious when visiting the page.

@BeryJu suggested that the bug is due to our using `{...}` to symbolize parameters in a URL while
Docusaurus wants to interpret `{...}` as an internal template instruction, resulting in odd
behavior. In either case, docusarus interpreted the hashtagged entries as links to unrelated issues
in Github (the same two issues, which were "bump version of pylint" and "bump version of sentry"),
which could be very confusing.

The inconsistencies between the two releases, and the working releases, suggests that the error was
introduced manually.

* web/maintenance: lint pass to add missing HTMLElementTagNameMap entries

# What

This code mechanically adds HTMLElementTagNameMap entries to those files that were missing it.

Every entry in the report is in this format:

    ./src/elements/ak-table/stories/ak-select-table.stories.ts

        'ak-select-table-test-sort' has not been registered on HTMLElementTagNameMap
        84:  export class SimpleTableSortTest extends LitElem
        no-missing-element-type-definition

It was trivial to create a Perl script that extracted the file name, the tag name, and the class name, and turn that into a “Open this file and append the HTMLElementTagNameMap definition to the end,” then run `prettier` and `build` to validate that nothing broke.

I also had to hand-edit the JSDoc for `Form`. It is not, by itself, an element. It is an abstract class from which you can derive elements. The `@element` tag there confused lit-analyze, and lit-analyze was correct to call it out.

# Why

These entries help Typescript & Lit-Analyze lint our product, validating that each element is being used correctly and that the types being passed to it are correct.
@GirlBossRush GirlBossRush force-pushed the cherry-pick/18950-to-version-2025.12 branch from d324e4c to 2ed5c70 Compare January 22, 2026 14:14
@BeryJu BeryJu disabled auto-merge January 22, 2026 14:25
@BeryJu BeryJu merged commit 22d0974 into version-2025.12 Jan 22, 2026
63 of 90 checks passed
@BeryJu BeryJu deleted the cherry-pick/18950-to-version-2025.12 branch January 22, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants