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.

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

fix(core): Add payment_link_data in PaymentData for Psync #7205

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

cookieg13
Copy link
Contributor

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Hotfix for 7137

Additional Changes

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

@cookieg13 cookieg13 requested a review from a team as a code owner February 6, 2025 16:15
Copy link

semanticdiff-com bot commented Feb 6, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  crates/router/src/core/payments.rs  0% smaller
  crates/router/src/core/payments/operations/payment_status.rs  0% smaller

@cookieg13 cookieg13 changed the title fix(core): Add payment_link_data in PaymentData for Psync (#7137) fix(core): Add payment_link_data in PaymentData for Psync Feb 6, 2025
@cookieg13 cookieg13 changed the base branch from main to hotfix-2025.02.05.0 February 6, 2025 16:26
@cookieg13 cookieg13 self-assigned this Feb 6, 2025
@likhinbopanna likhinbopanna merged commit 60f5a3e into hotfix-2025.02.05.0 Feb 7, 2025
25 of 29 checks passed
@likhinbopanna likhinbopanna deleted the psync-fix-hotfix branch February 7, 2025 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants