Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2024.49.0 #1824

Merged
merged 55 commits into from
Dec 3, 2024
Merged

Release 2024.49.0 #1824

merged 55 commits into from
Dec 3, 2024

Conversation

kasperg
Copy link
Contributor

@kasperg kasperg commented Dec 3, 2024

No description provided.

kasperg and others added 30 commits November 5, 2024 13:51
The current approach is somewhat frail in regards to ensuring
correct and consistent formatting.

In practice it also has challenges given the fact that it requires us
to ensure that our values are properly encoded. We have currently done
this for the description but in practice we also need to do this for
all other values.

To avoid this we update the implementation to use core PHP XML Writer
instead.

It has a number of advantages over alternate solutions:

- SimpleXML does not allow the same amount of control of the output.
Example; I could not get it to add an explicit encoding attribute on
the root XML element.
- Third party solutions add to our dependency tree. We do not want to
do this to maintain a legacy solution.

The new implementation has been checked by matching it with the
existing one using semantic diff'ing with difftastic.

It matches 1-to-1 except for the following exception: When data is
missing e.g. branch or media then the related elements are omitted
instead of returning empty elements.

By doing this we can drop the encoding of the description we already
added.
It should be medium - not contentmedium.
Sometimes we want to display ranges of prices in situations where it
is not appropriate to apply the additional formatting that we normally
do (current prefix, "free" instead of 0 etc.)

One example for this is the RSS feed for the Redia app.

This adds support for this supported by a unit test.
Prices in the original feed are (mostly) displayed as raw integers in
the format "[price]" or "[low price] - [high price]". If the event is
free then there is no price element for it in the feed.

Add support for similar output in the our new implementation of the
feed by using the raw price range formatting.
…ER-132

As we use inheritance, we want an updated series to also reflect in the
updatedAt API property.
We could implement this, by programmatically saving all instances when
the series is saved, but this may have unforseen consequences, as it is
running against the Drupal system.
Instead, we'll look up the instance and series changed dates, and take
which ever is newer.
NOTE: We need to find the proper settings in PR/prod as well
It is error prone and confusing to use multiple domain names.
Plus reload/https-proxy image in docker-compose.dev.yml is set to use
that domain for https
…-til-at-kore-med-https-og-opsaet-cors-configuration
…saet-dpl-cms-dapple-cms-docker-til-at-kore-med-https-og-opsaet-cors-configuration

No CORS + Https
Bumps drupal/admin_toolbar from 3.5.0 to 3.5.1.

---
updated-dependencies:
- dependency-name: drupal/admin_toolbar
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps drupal/antibot from 2.0.3 to 2.0.4.

---
updated-dependencies:
- dependency-name: drupal/antibot
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
It has previous been uninstalled and can now be removed from the
project codebase.
…composer/drupal/admin_toolbar-3.5.1

Bump drupal/admin_toolbar from 3.5.0 to 3.5.1
…composer/drupal/antibot-2.0.4

Bump drupal/antibot from 2.0.3 to 2.0.4
kasperg and others added 24 commits November 27, 2024 12:33
…event-api-changed

Update event API, editing series should reflect in changed date. DDFHER-132
In the dpl-react project, we migrated from `/holdings/v3` to `/holdingsLogistics/v1`. Refer to the pull request: danskernesdigitalebibliotek/dpl-react#1443.

This change caused the `user-journey` Cypress test to fail.
The previous configuration was using release `2024.48.0`, but it must be switched back to `develop` to include the `/holdingsLogistics/v1` update.

This adjustment is essential for other developers' work until the next release.
…mplementer-nyt-beholdnings-endpoint

DDFHER-83 - Update Cypress fixtures to reflect the new `/holdingsLogistics/v1` API
# Conflicts:
#	web/modules/custom/dpl_event/src/EventWrapper.php
Bumps the minor-js-dependencies group with 2 updates: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) and [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser).


Updates `@typescript-eslint/eslint-plugin` from 8.16.0 to 8.17.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.17.0/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 8.16.0 to 8.17.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.17.0/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-js-dependencies
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-js-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
When updating a user, we want to log the changes done - this is part of
a security policy by DDF.
For most fields, the old and new value gets logged, but others may be
ignored, or declared on a meta-level (such as password).
…npm_and_yarn/minor-js-dependencies-263190dbf1

Bump the minor-js-dependencies group with 2 updates
…user-logging

Logging custom DDF events, such as updates to users. DDFHER-150
…expand-event-api

Expand event API to include `partners` as array string. DDFHER-119
…o-version

Rolling back from incompatible go version
…4.49.0

Use release 2024.49.0 of design system and React components
@kasperg kasperg merged commit f36e53e into main Dec 3, 2024
21 checks passed
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.

6 participants