Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike: Research more developer-friendly way of managing validate version changes #335

Open
exalate-issue-sync bot opened this issue Feb 6, 2025 · 0 comments
Open

Spike: Research more developer-friendly way of managing validate version changes #335

exalate-issue-sync bot opened this issue Feb 6, 2025 · 0 comments
Assignees
@toddlees

Comments

@exalate-issue-sync
Copy link

While running the release cut for sprint 55,Todd Lees was going to add instructions for updating the deployment instructions to update the commit hash for the validator in the api and the web app, and as we were discussing it, it’s not a very friendly process during deploys. It’s worth revisiting how we manage these going into production.

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-2008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toddlees toddlees

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toddlees