Skip to content

fix: Only set valid timezone values#1049

Merged
come-nc merged 1 commit intomasterfrom
fix/fix-timezonecontroller
Mar 17, 2026
Merged

fix: Only set valid timezone values#1049
come-nc merged 1 commit intomasterfrom
fix/fix-timezonecontroller

Conversation

@come-nc
Copy link
Contributor

@come-nc come-nc commented Mar 17, 2026

No description provided.

Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
@come-nc come-nc self-assigned this Mar 17, 2026
@come-nc come-nc requested review from Altahrim, artonge and blizzz March 17, 2026 16:39
@come-nc
Copy link
Contributor Author

come-nc commented Mar 17, 2026

/backport to stable33

@come-nc
Copy link
Contributor Author

come-nc commented Mar 17, 2026

/backport to stable32

@come-nc
Copy link
Contributor Author

come-nc commented Mar 17, 2026

/backport to stable31

@come-nc come-nc merged commit 46b1dc6 into master Mar 17, 2026
71 of 72 checks passed
@come-nc come-nc deleted the fix/fix-timezonecontroller branch March 17, 2026 17:08
@backportbot
Copy link

backportbot bot commented Mar 17, 2026

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/1049/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1d7de7bc

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/1049/stable31

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/1049/stable31')
fatal: not a valid object name: 'origin/stable31'


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot
Copy link

backportbot bot commented Mar 17, 2026

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/1049/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1d7de7bc

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/1049/stable32

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/1049/stable32')
fatal: not a valid object name: 'origin/stable32'


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot
Copy link

backportbot bot commented Mar 17, 2026

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/1049/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1d7de7bc

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/1049/stable33

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/1049/stable33')
fatal: not a valid object name: 'origin/stable33'


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@come-nc
Copy link
Contributor Author

come-nc commented Mar 17, 2026

No backports needed, master branch supports 30 to 33.

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