Stage Release #3872
Merged
Stage Release #3872
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…efined (#3853) Prevent app from crashing when item versions is null or undefined due to the api call to fetch a content item's versions fail Resolves #3831 [Screencast_20251016_115118.webm](https://github.com/user-attachments/assets/58afa838-970b-45aa-95f8-65971df16618)
Preserves user selected values on the CSV import headers even if the user scrolls Resolves #3832 [Screencast_20251014_111945.webm](https://github.com/user-attachments/assets/da5a3004-6e9f-4fd9-af09-60499550d189) --------- Co-authored-by: Andres <agalin920@gmail.com>
…s been deleted (#3839) Block the ff actions if a selected file has been deleted: - Preview File - Edit File - Rename File - Replace File - Copy ZUID - Copy URL Resolves #3830 <img width="767" height="178" alt="image" src="https://github.com/user-attachments/assets/fa1fd297-f44c-45ff-8852-e57f71bacb34" />
This PR significantly improves how event messages pertaining to user actions in sentry's breadcrumbs. Instead of a long list of element selector, this change would try to extract the relevant data from the element to make figuring out which elements were being interacted with by the user that lead to the sentry issue. The following element attributes are being extracted: - tag name - data-cy - element id - element name (for input type elements) - button text (for buttons) This change also enables `reactComponentAnnotation` in Sentry to help track which react components were being interacted with. For the above to work, sentry and its relevant packages also had to be upgraded. [Sample Sentry issue](https://zestyio.sentry.io/issues/6951028253/?environment=development&project=5441698&query=is%3Aunresolved&referrer=issue-stream) with this formatting enabled ###⚠️ Minor Con Due to `reactComponentAnnotation` being enabled, this increases the build time when making **stage** and **production** builds since babel has to go through each relevant file and add the relevant sentry attributes. ### Sample formatted event messages <img width="1920" height="1052" alt="Screenshot_20251017_133545" src="https://github.com/user-attachments/assets/4d5027d9-91d2-4f92-aaf9-5631550f4eb5" />
This PR introduces per-suite data seeding to significantly enhance the stability of our test runs. Currently, concurrent CI pipeline runs can lead to data clashing when tests modify or rely on the same shared database records. This change seeds a unique, isolated dataset for each suite execution, effectively eliminating the risk of data conflicts and reducing intermittent test failures. **Note**: We rely on the nightly sync to overwrite the downstream environment changes. Effectively acting as our **cleanup process**. Otherwise the data generation while seeding would build up overtime eventually becoming problematic. Key changes: - Data isolation: introduce a new pattern for seeding data before a test spec is ran. - plugin: introduce the usage of cypress plugins - - by using plugins we can allow for work to happen within the nodejs process when cypress initial starts, before code execution in the headless browser - add: auth function during seeding - add: content fixture data - add: node-sdk - update: content.spec.js element selection and view navigation to work with dynamic data generation from seeding. --------- Co-authored-by: geodem <geodem.dev@gmail.com>
Resolves an issue where an early render is sometimes causing the component to render with fewer hooks Fixes #3854
Removes custom hook that was fetching content items and publishings and instead utilizes existing store/indexdb system to select and hydrate on search
shrunyan
approved these changes
Nov 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by Github action