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 2025.2.0 #1927

Merged
merged 116 commits into from
Jan 7, 2025
Merged

Release 2025.2.0 #1927

merged 116 commits into from
Jan 7, 2025

Conversation

kasperg
Copy link
Contributor

@kasperg kasperg commented Jan 7, 2025

No description provided.

xendk and others added 30 commits September 13, 2024 11:47
Bumps [nanoid](https://github.com/ai/nanoid) from 3.3.6 to 3.3.8.
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@3.3.6...3.3.8)

---
updated-dependencies:
- dependency-name: nanoid
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
…npm_and_yarn/nanoid-3.3.8

Bump nanoid from 3.3.6 to 3.3.8
This field will be used to keep track of which articles have been
imported to/from BNF already.
The importer will take the original node UUID and place it here.
Technically, this will be a read-only field, as we never want the user
to actually edit it, but I still decided to introduce it as a regular
node field as it will make debugging in the future much easier if we
have access to it, through the Drupal interface.
Creating a custom mutation graphQL endpoint, as part of the `bnf_server`
module.
This endpoint will receive a ping from client libraries, when they want
a certain node of theirs to be imported to BNF.
The client will send along a UUID and an endpoint which BNF can use to
do a GraphQL query against, to get the node data.
Introduce an importer service to the `bnf` common module.
This service takes the info that we received from the client ping, and
calls the supplied GraphQL source, parses the fields, and creates a
node.
This service will also be used in the future when the client wants to
import a peice of content from BNF.
Expanding the ImportRequest graphQL endpoint to actually attempt to
import the node that the client has supplied data about.
…-opgrader-markdownlint-cli-2

PR for danskernesdigitalebibliotek/dpl-design-system:DDFNEXT-202-opgrader-markdownlint-cli-2
…-nvmrc-file

feat: add .nvmrc file specifying Node.js version 20
A service with a single method, that is used to programmatically connect
to the BNF ImportRequest graphQL endpoint.
Adding a simple form field to the node edit form, with a checkbox.
If the checkbox is checked, the node will be published and sent to BNF
upon save.
Originally, I wanted to have a "publish to BNF" button, but that became
very complicated, as I'd have to replicate some of the submit handling
that happens with the core "submit" button.
In the end, I think this solution is user friendly enough.
For debugging sakes, I prefer not to hide modules in the interface.
None of our BNF modules will be enabled manually, regardless.
This uses environment variables, that we also need to set on lagoon.
Ontop of that, we set the GraphQL calls to be HTTPS.
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.18.0 to 8.18.1
- [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.18.1/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 8.18.0 to 8.18.1
- [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.18.1/packages/parser)

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

Signed-off-by: dependabot[bot] <[email protected]>
Bumps drupal/administerusersbyrole from 3.4.0 to 3.5.0.

---
updated-dependencies:
- dependency-name: drupal/administerusersbyrole
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps drupal/override_node_options from 2.8.0 to 2.9.0.

---
updated-dependencies:
- dependency-name: drupal/override_node_options
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
kasperg and others added 26 commits January 3, 2025 11:14
…npm_and_yarn/minor-js-dependencies-21033d1065

Bump the minor-js-dependencies group across 1 directory with 3 updates
…composer/minor-composer-dependencies-89f2326100

Bump spatie/color from 1.6.2 to 1.7.0 in the minor-composer-dependencies group across 1 directory
…he-static-files

Reenable caching of static files in Varnish
Docker compose defaults to using the directory name and hardcoding it
makes running two instances troublesome.
The TLD used depends on the developers setup, some use `docker`,
others `local`, so make it configurable.
It just prints out a few links when composer installing.
This mirrors a change introduced for the site templates in
dpl-platform.

While most core sites will not need the additional storage increasing
the storage limit will not introduce additional costs. Having the
same limit as production sites ensures that we avoid hitting the limit
if we need to synchronise data from a production site to a PR site.
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.19.0 to 8.19.1
- [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.19.1/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 8.19.0 to 8.19.1
- [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.19.1/packages/parser)

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

Signed-off-by: dependabot[bot] <[email protected]>
Bumps drupal/gin_toolbar from 1.0.0-rc8 to 1.0.0.

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

Signed-off-by: dependabot[bot] <[email protected]>
…npm_and_yarn/minor-js-dependencies-ed1a13d9b2

Bump the minor-js-dependencies group with 2 updates
…persistent-size

Increase size of NGINX persistent storage to 10Gi
…composer/drupal/gin_toolbar-1.0.0

Bump drupal/gin_toolbar from 1.0.0-rc8 to 1.0.0
…5.2.0

Use release 2025.2.0 of design system and React components
@kasperg kasperg merged commit 428c4cf into main Jan 7, 2025
22 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.

7 participants