Skip to content

Staging - #141

Open
matej-marcisovsky wants to merge 11 commits into
mainfrom
staging
Open

matej-marcisovsky wants to merge 11 commits into
mainfrom
staging

Conversation

@matej-marcisovsky

Copy link
Copy Markdown
Collaborator

Task Link

Task #

Description

What are the changes and why have they been made.

For FE components/blocks: Please directly link the Figma design you are referencing.

TL;DR

What's the TLDR?

Screenshots/Videos

Include images or videos to show the feature you've implemented. (if applicable, mostly for frontend components)

For FE blocks: Please attach screenshots of the FE component being implemented through the CMS.

New environmental variables

If your PR introduces new environment variables, please list them here along with a description of their use and apply the requires-env-vars label.

Checklist - author

  • Assignee is set (the active developer of this PR).
  • Reviewers are set (team members who will review the code).
  • PR is linked I have linked the PR to an issue in Jira.
  • Description I have described the changes proposed in the PR clearly and concisely (more important than what is why).
  • Screenshots/Videos I have added screenshots/videos or they were not needed.
  • Environmental variables are listed or they were not needed.
  • Unit/Integration tests are added for all utilities and business important logic
  • Labels I have added labels to the PR.
    • Use requires-env-vars when PR requires environmental variables
    • Use ready-for-review when PR is ready to be looked at
    • Use ready-to-merge when PR has a passing review
    • Use needs-revisions when PR has comments that block merge
    • Use do-not-review when PR is daft only and you don't want to get a review
  • [OPTIONAL] Conversation/documentation is started in places where the code is not self-explanatory

Before merging

  • PR is approved
  • All conversations are resolved
  • Pipelines are not failing

Checklist - reviewer

  • I understand all proposed changes.
  • Necessary after deploy steps are handled by someone (adding new env var, syncing config, running migration...)

@vercel

vercel Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
website-ui Ready Ready Preview Oct 5, 2026 9:07am UTC
website-ui (staging) Ready Ready Preview Oct 5, 2026 9:07am UTC

Request Review

…version-update

131 create automation for strapi version update

This branch was successfully deployed

1 active deployment
staging — e9246fbc Deployed Oct 5, 2026 by vercel[bot]
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.

1 participant