Conversation
* WIP * project audit log * table updates * cleanup * modal * UX improvements * exclude outline class from Tailwind due to Semantic UI conflict * fix styling inconsistency * update label * update gem
…ents Bump connector and triple-eye-effable (#647)
* add primary domain redirect middleware * more info in example env
Allow paginated and whitespace-tokenized keyword search queries in relational dropdowns (#644)
…-token Bump core-data-connector to v0.2.3
* feedback WIP * fix edit button condition * update CDC
* move gems over * copy files * config
Remove unwanted fields from AtoM identifier modal
…-record-names Autofocusing on record name dropdown in related record modals
* WIP published toggle * publish button * default published state for projects * testing SSH key fix again lol * restrict public endpoints to published records * Typesense and UI tweaks * fix unpublished records appearing in relationship fields
…nship-import Fix `result` field on merged relationship data to avoid import bug
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
blms
left a comment
There was a problem hiding this comment.
I agree some smoke testing is a good idea!
There was a problem hiding this comment.
Tomorrow morning would be good for a production release. There are some manual steps involved for the domain change but it shouldn't be too substantial.
The app will still be served on app.coredata.cloud with middleware that redirects all requests to the new domain while preserving the path. So e.g. the FairData Sites sites that pull data from the public endpoints will still work.
In this PR
Release candidate. Includes the following PRs:
resultfield on merged relationship data to avoid import bug #671See PR #649 for notes on some environment variable tweaks that are needed to go along with updating the main domain to be on Performant Studio. I believe each of these features has been tested individually but we may want to do a bit of tire-kicking on staging to make sure things are playing nicely together? I'm also not sure if there's anything to be considered about updating the domain in other apps that reference it, or whether the
app.coredata.clouddomain will still work fine for now.