chore: prepare v8.28.0

[susnux]

v8.28.0 (2025-07-14)

📝 Notes

NcPasswordField

The component now has a visible property (with update:visible event) to allow setting the visibility state of the password.
This allows to programmatically make the password visible or obfuscated for the user.
One use case could be to reset the visibility when submitting some form to prevent leaking the password in a loading state of the UI.

NcTextField

The value arrowRight of the property trailingButtonIcon is deprecated and will be removed in a future version.
It is replaced by arrowEnd which reflects that the directions depends on the text directions (LTR vs RTL).

NcColorPicker

The update:open event is deprecated, instead just use the close event which is emitted at the same time.

Event names

Custom events now have a consistent naming without custom scoping of the events.
Thus following events are deprecated in favor of a new consistent event name:

Component	Old event	New event
NcAppContent	resize:list	resize-list
NcRichText	interact:todo	interact-todo

🚀 Enhancements

• feat: add useFormatRelativeTime composable #7128 (backportbot[bot])
• feat(NcPasswordField): allow to set visibility state #7148 (backportbot[bot])

🐛 Fixed bugs

• fix(NcAppNavigationItem): multi level padding #6919 (backportbot[bot])
• fix(NcTextField): make trailing button icon for confirmation also work on RTL #7002 (backportbot[bot])
• fix(NcAppContent): incorrect page title from a different core.apps format in Nextcloud 30 #7011 (julien-nc)
• fix(NcDialog): deprecated nativeType usage check #7031 (skjnldsv)
• fix(NcSelectUsers): fix using of v-model in Vue 2 #7032 (Antreesy)
• fix(NcAvatar): update 'hasStatus' flag if changed #7037 (backportbot[bot])
• fix(NcCheckboxRadioSwitch): align icons with the first row of label #7047 (backportbot[bot])
• fix(actions): use pointer cursor for action button text #7049 (backportbot[bot])
• fix(NcRichText): always render code blocks in LTR direction #7061 (Antreesy)
• fix(NcListItem): let active prop take higher priority #7089 (backportbot[bot])
• fix(NcActionText): remove br between action name and action long text #7119 (backportbot[bot])
• fix(useHotKey): try to derive latin keys from key codes of non-latin characters #7147 (backportbot[bot])

Other Changes

• refactor: deprecate events not comply with Vue event naming rules #7078 (backportbot[bot])
• chore(NcColorPicker): deprecate duplicated update:open event #7095 (backportbot[bot])
• chore(NcActions): fix type annotation of NodeList #7105 (backportbot[bot])
• chore(NcAppContent): rename NcAppDetailsContent to remove from docs #7139 (backportbot[bot])
• refactor(NcAppContent): clarify props documentation and use capabilities over initial state #7141 (backportbot[bot])

[Antreesy]

• fix(l10n): adjust for @nextcloud/l10n v3.4.0 #7131 is missing from stable release. Can we get this backported as well?

[ShGKme]

But this is not a breaking change or something developers need to pay attention to.

Seems to be a general new feature for a specific use case.

[susnux]

@Antreesy asked for it :)

[Antreesy]

IMO we should always be descriptive and inform about:

• breaking changes;
• deprecated things;
• new features.

Although a one-liner what it's for would be enough =)

[ShGKme]

• new features.

They are already listed in the dedicated 🚀 Enhancements section 👀

I think, it makes sense to add a long note about a new feature, if it's something big, that requires additional attention. Such as a new component that should be used instead of existing.

Here, for instance, useFormatRelativeTime partically replacing moment seems much more important than a new prop in the password field.

Although a one-liner what it's for would be enough =)

We have one line description at home in the changelog: allow to set visibility state from the PR title. Seems fine to me.

Can also be more detailed to explicitply mention new prop like:

• feat(NcPasswordField): add visible model to set password visibility state

[Antreesy]

Tested

[ShGKme]

All the notes are missing in the release notes