-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Release to val #470
Merged
Release to val #470
Conversation
This file contains 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
…n withdraw (#466) * feat(modify rai behavior): For all types, go back to pending rai on withdraw, and do not nullify received * Add verbose logging to response, since we are now potentially overwriting data that was directly touched in seatool * Make logging more verbose * fix the dashboard to show received date regardless of withdraw status
…o our app, and add support for legacy TEs (#452) * integrate legacy package actions * fix test, but i think its sort of self defeating now. need to leverage the actual function * devOrigin add * fix changeDate * a * make it faster * legacyinsishgts * move maprole out of reindex for speed * retry bulk update with exponential backoff * correct legacy insights * functional. however, deletes in legacy are not knocking out their old changelog events. in addition, some of the events are misconstructed. we may want to maintain main from the more consistently structured 'package' events, and populate the changelog from the sumbit events. * Remove... not safe to do, and its actuallys lower than just letting os process them all. * solution for hard deletes from legacy * im on the fence on this... id like an event that shows the hard delete, but we dont need it, and hard deletes are something were simply not going to do... so i think less may be more here * handle legacy hard deletes in main * cover more events * hold * move back to package view for main * ok * add TE support to main * Means of marking a record as deleted * fix up legacy insights... TEs are now identifal counts * FOLLOWUP... why * comments * Fix unit test * rm debug * rm debug * Remove double function call for readability * updating the status so im less confused later * Removing line for good * remove uneeded else * abstract some props * test * Walk back updating new=-submission to actions... i want to take our time on that one * bump * only use timestamp filter for legacy, since its the only one with hard deletes * typo * separate action for rai withd rae request * deduplicate * yut * update creds * fix * hold * func * Update filter to return onemac or seatool * Updates, including moving all adminChange support to the materialize bit * unneeded * unneeded * Refactor some * Rm * Add types * remove devOrigin and use legacy withdraw rai request * Add TE_PENDING as a new seatool status * lint... why is my linter hot than its cold, yes than its no. * fix logic so when component type is not defined it behaves correctly * Conditionally render Changed Reason * Fix status * bump
mdial89f
approved these changes
Mar 26, 2024
🎉 This PR is included in version 1.5.0-val.20 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Release to val.
Please create a merge commit