release 0.49.0 #3477

RenkuBot · 2024-02-07T14:25:19Z

Release 0.49.0

This PR is auto-generated by actions/github-script.

/deploy

RenkuBot · 2024-02-07T14:28:33Z

You can access the deployment of this PR at https://ci-renku-3477.dev.renku.ch

* chore: scalafmt upgraded to 3.8.0 * chore: selenium-java upgraded to 4.18.1

* chore: sbt upgrade to 1.9.9 * chore: pureconfig update to 0.17.6

Bumps [python-keycloak](https://github.com/marcospereirampj/python-keycloak) from 3.7.0 to 3.9.0. - [Changelog](https://github.com/marcospereirampj/python-keycloak/blob/master/CHANGELOG.md) - [Commits](marcospereirampj/python-keycloak@v3.7.0...v3.9.0) --- updated-dependencies: - dependency-name: python-keycloak dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Rok Roškar <[email protected]>

Bumps [python-keycloak](https://github.com/marcospereirampj/python-keycloak) from 3.7.0 to 3.9.1. - [Changelog](https://github.com/marcospereirampj/python-keycloak/blob/master/CHANGELOG.md) - [Commits](marcospereirampj/python-keycloak@v3.7.0...v3.9.1) --- updated-dependencies: - dependency-name: python-keycloak dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Rok Roškar <[email protected]>

Refreshes #2894 and supercedes it. Co-authored-by: Ralf Grubenmann <[email protected]>

Co-authored-by: Laura <[email protected]> Co-authored-by: M. Alisafaee <[email protected]> Co-authored-by: Jakub Chrobasik <[email protected]> Co-authored-by: Ralf Grubenmann <[email protected]>

leafty

Please fix the merge conflict before releasing.

leafty · 2024-03-05T12:47:07Z

.github/workflows/renku-dev-test.yaml

@@ -23,7 +23,7 @@ jobs:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/[email protected]
-      - uses: cypress-io/github-action@v6
+      - uses: cypress-io/github-action@v5


huh?

Suggested change

- uses: cypress-io/github-action@v5

- uses: cypress-io/github-action@v6

leafty · 2024-03-05T12:47:23Z

CHANGELOG.rst

+
+The release contains bug fixes to renku core service related to project migration.
+
+This release also contains initial support for next generation 'Renku 1.0' functionality. However,


Here and everywhere else:

Suggested change

This release also contains initial support for next generation 'Renku 1.0' functionality. However,

This release also contains initial support for next generation 'Renku 2.0' functionality. However,

I will make a PR to update Renku 1.0 references for the whole changelog

leafty · 2024-03-05T12:48:44Z

RELEASE.md

@@ -12,9 +12,8 @@ This procedure should be followed for *any* release:

 * Create a release branch (e.g. `0.46.x`), if one does not already exist, with the [release action](https://github.com/SwissDataScienceCenter/renku/actions/workflows/create-release-branch.yml).
 * Create a `CHANGELOG` entry for the release and open a PR; create a deployment, this is the reference for the release.
-* Note that any PR that should go into the release needs to target the release branch _not_ `master`.
+* Note that any PR that should go into the release needs to target the release branch _not_ `master`. 


Suggested change

* Note that any PR that should go into the release needs to target the release branch _not_ `master`.

* Note that any PR that should go into the release needs to target the release branch _not_ `master`.

leafty · 2024-03-05T12:53:48Z

helm-chart/renku/templates/NOTES.txt

@@ -9,7 +9,7 @@ can be accessed using the following one-liner (you need to have jq installed).
 kubectl get secrets -n {{ .Release.Namespace }} {{ template "renku.fullname" . }} -o json | jq -r .data.users | base64 --decode
 {{- end -}}

-{{ if or .Values.ui.client.privacy.banner.enabled .Values.ui.client.privacy.page.enabled -}}
+{{ if .Values.ui.client.privacy.enabled -}}


This looks like a merge conflict wrongly resolved.

leafty · 2024-03-05T12:55:27Z

docs/how-to-guides/admin/privacycookie.rst

This file looks like it was badly merged too.

leafty · 2024-03-05T12:57:36Z

helm-chart/values.yaml.changelog.md

@@ -16,6 +62,8 @@ The handling of privacy policy and terms of service content has been fine tuned.
 * NEW ``ui.client.privacy.page.termsContent`` to customize the content of the Terms of Use page (supports Markdown).


+=======
+>>>>>>> 4a49d877 (chore: update values changelog)


Unresolved git merge conflict!!!

leafty

Merge conflicts seem fixed

RenkuBot requested a review from a team as a code owner February 7, 2024 14:25

RenkuBot added the release label Feb 7, 2024

RenkuBot temporarily deployed to ci-renku-3477 February 7, 2024 14:25 — with GitHub Actions Inactive

RenkuBot requested a review from a team as a code owner February 19, 2024 08:45

RenkuBot and others added 3 commits February 21, 2024 14:59

chore: create release 0.49.0

8079be1

chore: logback update to 1.5.0 (#3500)

89811a8

chore: scalafmt and selenium-java upgrades (#3504)

924369b

* chore: scalafmt upgraded to 3.8.0 * chore: selenium-java upgraded to 4.18.1

rokroskar force-pushed the release-0.49.0 branch from e69ab29 to 924369b Compare February 21, 2024 14:00

rokroskar temporarily deployed to ci-renku-3477 February 21, 2024 14:00 — with GitHub Actions Inactive

Merge branch 'master' into release-0.49.0

f365013

rokroskar temporarily deployed to ci-renku-3477 February 22, 2024 12:28 — with GitHub Actions Inactive

chore: selenium tests libs upgrade (#3516)

8ae46dc

* chore: sbt upgrade to 1.9.9 * chore: pureconfig update to 0.17.6

jachro temporarily deployed to ci-renku-3477 February 23, 2024 08:17 — with GitHub Actions Inactive

Merge branch 'master' into release-0.49.0

be30381

rokroskar temporarily deployed to ci-renku-3477 February 23, 2024 12:03 — with GitHub Actions Inactive

Update from auto-update/renku-core-2.9.2 (#3472)

45ecfd5

RenkuBot requested a review from a team as a code owner February 23, 2024 13:11

Panaetius temporarily deployed to ci-renku-3477 February 23, 2024 13:12 — with GitHub Actions Inactive

rokroskar temporarily deployed to ci-renku-3477 February 27, 2024 12:24 — with GitHub Actions Inactive

chore: scala update to 2.13.13 (#3519)

b7cf6b9

jachro temporarily deployed to ci-renku-3477 February 27, 2024 13:01 — with GitHub Actions Inactive

olevski had a problem deploying to ci-renku-3520 February 28, 2024 09:52 — with GitHub Actions Error

chore: Update logback-classic from 1.4.14 to 1.5.1 (#3522)

9b36946

jachro temporarily deployed to ci-renku-3477 February 29, 2024 08:31 — with GitHub Actions Inactive

chore: bump csi-rclone (#3523)

85df5c5

RenkuBot requested a review from a team as a code owner March 1, 2024 08:06

Panaetius temporarily deployed to ci-renku-3477 March 1, 2024 08:06 — with GitHub Actions Inactive

chore: Update logback-classic from 1.4.14 to 1.5.2 (#3524)

913a68e

jachro temporarily deployed to ci-renku-3477 March 4, 2024 08:33 — with GitHub Actions Inactive

rokroskar temporarily deployed to ci-renku-3477 March 4, 2024 15:33 — with GitHub Actions Inactive

chore: Update logback-classic from 1.4.14 to 1.5.3 (#3527)

67b4dc3

jachro temporarily deployed to ci-renku-3477 March 5, 2024 08:38 — with GitHub Actions Inactive

chore(postgres): Upgrade Postgres to version 16.1.0 (#3170)

6fc71b6

Refreshes #2894 and supercedes it. Co-authored-by: Ralf Grubenmann <[email protected]>

aledegano had a problem deploying to ci-renku-3477 March 5, 2024 09:33 — with GitHub Actions Failure

feat: renku native projects (#3376)

f279922

Co-authored-by: Laura <[email protected]> Co-authored-by: M. Alisafaee <[email protected]> Co-authored-by: Jakub Chrobasik <[email protected]> Co-authored-by: Ralf Grubenmann <[email protected]>

olevski had a problem deploying to ci-renku-3477 March 5, 2024 12:30 — with GitHub Actions Failure

olevski temporarily deployed to ci-renku-3477 March 5, 2024 12:51 — with GitHub Actions Inactive

leafty requested changes Mar 5, 2024

View reviewed changes

leafty reviewed Mar 5, 2024

View reviewed changes

change from renku 1.0 to 2.0

3a36e8f

lokijuhy temporarily deployed to ci-renku-3477 March 5, 2024 13:25 — with GitHub Actions Inactive

fix merge conflicts

6ad6f12

Panaetius deployed to ci-renku-3477 March 5, 2024 13:46 — with GitHub Actions View deployment

aledegano approved these changes Mar 5, 2024

View reviewed changes

leafty approved these changes Mar 5, 2024

View reviewed changes

lokijuhy approved these changes Mar 5, 2024

View reviewed changes

lokijuhy merged commit ec031d0 into master Mar 5, 2024
19 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

release 0.49.0 #3477

release 0.49.0 #3477

RenkuBot commented Feb 7, 2024

RenkuBot commented Feb 7, 2024

leafty left a comment

leafty Mar 5, 2024

leafty Mar 5, 2024

lokijuhy Mar 5, 2024

leafty Mar 5, 2024

leafty Mar 5, 2024

leafty Mar 5, 2024

leafty Mar 5, 2024

leafty left a comment

	- uses: cypress-io/github-action@v5
	- uses: cypress-io/github-action@v6


		The release contains bug fixes to renku core service related to project migration.

		This release also contains initial support for next generation 'Renku 1.0' functionality. However,

	* Note that any PR that should go into the release needs to target the release branch _not_ `master`.
	* Note that any PR that should go into the release needs to target the release branch _not_ `master`.

release 0.49.0 #3477

release 0.49.0 #3477

Conversation

RenkuBot commented Feb 7, 2024

RenkuBot commented Feb 7, 2024

leafty left a comment

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

lokijuhy Mar 5, 2024

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

leafty Mar 5, 2024

Choose a reason for hiding this comment

leafty left a comment

Choose a reason for hiding this comment