[2.x] Existing databases do not receive order_lines.refunded_quantity for line-item refunds

[tazzytazzy]

Which release line(s) does this affect?

2.x

Lunar version

2.x - 32ed8e6

PHP version

8.5.9

Laravel version

13.29.0

Database driver & version

MariaDB 11.8.8

Expected behaviour

After upgrading an existing Lunar 2.x database and running the documented migration process, its schema should match a fresh installation.

Specifically:

• order_lines.refunded_quantity should be added as an unsigned integer with a default of 0.
• Existing order-line records should be preserved and receive the default value.
• A line-item refund should create the refund transaction and corresponding refund_lines records, increment refunded_quantity, and dispatch OrderRefunded.

Actual behaviour

After upgrading an existing Lunar 2.x database and running the documented migration process, its schema should match a fresh installation.

Specifically:

• order_lines.refunded_quantity should be added as an unsigned integer with a default of 0.
• Existing order-line records should be preserved and receive the default value.
• A line-item refund should create the refund transaction and corresponding refund_lines records, increment refunded_quantity, and dispatch OrderRefunded.

Minimal reproduction steps

After upgrading an existing Lunar 2.x database and running the documented migration process, its schema should match a fresh installation.

Specifically:

• order_lines.refunded_quantity should be added as an unsigned integer with a default of 0.
• Existing order-line records should be preserved and receive the default value.
• A line-item refund should create the refund transaction and corresponding refund_lines records, increment refunded_quantity, and dispatch OrderRefunded.

[github-actions]

Thanks for the report. Before this can be looked into, we need a bit more detail:

• actual_behaviour
• reproduction_steps

Once that's added a maintainer can pick it up. Without it we can't reproduce the problem, and the issue will be closed after a fortnight — that's no reflection on the report, we just can't action it as it stands.

---

Automated triage. Advisory only — a maintainer decides.

[tazzytazzy]

Thanks for the report. Before this can be looked into, we need a bit more detail:

• actual_behaviour
• reproduction_steps

Once that's added a maintainer can pick it up. Without it we can't reproduce the problem, and the issue will be closed after a fortnight — that's no reflection on the report, we just can't action it as it stands.

Automated triage. Advisory only — a maintainer decides.

This information was included in the original ticket.