-
Notifications
You must be signed in to change notification settings - Fork 464
Tags: lunarphp/lunar
Tags
1.3.0
Fix collection group resource permission (#2391)
![image]()
src="https://github.com/user-attachments/assets/cf79cd5b-3c77-4d49-8e09-270f8c1d6562"
/>
In Access control screen, Manage Collections permission is described to
manage collections and groups. however currently the menu/permission
follows Manage Products. This PR is to fix the permission to follow the
description
/>
In Access control screen, Manage Collections permission is described to
manage collections and groups. however currently the menu/permission
follows Manage Products. This PR is to fix the permission to follow the
description
1.0.1
Update ManageVariantIdentifiers breadcrumb to match correct page #1 (#...
...2274)
## Summary by CodeRabbit
* **Bug Fixes**
* Corrected breadcrumb navigation in the Product Variant admin area.
When managing variant identifiers, the final breadcrumb now links to the
Identifiers page instead of Inventory, aligning with the page context.
This improves navigation accuracy and consistency across the admin
interface, reducing confusion for users. No changes to data or
functionality--only the breadcrumb destination was updated wherever this
breadcrumb appears.
...2274)
## Summary by CodeRabbit
* **Bug Fixes**
* Corrected breadcrumb navigation in the Product Variant admin area.
When managing variant identifiers, the final breadcrumb now links to the
Identifiers page instead of Inventory, aligning with the page context.
This improves navigation accuracy and consistency across the admin
interface, reducing confusion for users. No changes to data or
functionality--only the breadcrumb destination was updated wherever this
breadcrumb appears.
1.0.0
v1.0.0 prep (#2273)
Updates documentation for v1.0.0 release
## Summary by CodeRabbit
* **Documentation**
* Removed beta cautions and production-readiness warnings across docs;
content reflects a 1.x/stable focus.
* Simplified installation guidance and reorganized advanced options
(telemetry moved under Advanced).
* Revamped upgrade guide into versioned 1.x roadmap with
alpha/beta/stable notes and migration guidance.
* Updated admin references to Filament and minor formatting
improvements.
* Removed "Initial Set-Up" and "Release Schedule" pages; adjusted
navigation.
* Trimmed security guidance and added support note: no full codebase
reviews.
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Updates documentation for v1.0.0 release
## Summary by CodeRabbit
* **Documentation**
* Removed beta cautions and production-readiness warnings across docs;
content reflects a 1.x/stable focus.
* Simplified installation guidance and reorganized advanced options
(telemetry moved under Advanced).
* Revamped upgrade guide into versioned 1.x roadmap with
alpha/beta/stable notes and migration guidance.
* Updated admin references to Filament and minor formatting
improvements.
* Removed "Initial Set-Up" and "Release Schedule" pages; adjusted
navigation.
* Trimmed security guidance and added support note: no full codebase
reviews.
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
1.0.0-beta25
Fix InvalidArgument in shipping options DTO (#2243)
Not sure why we were using
`Doctrine\Common\Cache\Psr6\InvalidArgument;`, I don't believe it's an
exception that's supposed to be used externally to the package. It also
no longer exists in the latest version.
## Summary by CodeRabbit
* **Refactor**
* Updated internal error handling to improve reliability when processing
shipping options. No changes to user-facing features.
---------
Co-authored-by: Author
Not sure why we were using
`Doctrine\Common\Cache\Psr6\InvalidArgument;`, I don't believe it's an
exception that's supposed to be used externally to the package. It also
no longer exists in the latest version.
## Summary by CodeRabbit
* **Refactor**
* Updated internal error handling to improve reliability when processing
shipping options. No changes to user-facing features.
---------
Co-authored-by: Author
1.0.0-beta24
Add vat number to db to all address tables (#2106)
The company's VAT number was not displayed at the order details (nor in
the generated PDF) on backend, and it should if the order was made by a
legal person.
Please check the related issue for more details:
#2070
As you suggested I added a new vat number field to the DB to all the 3
address tables.
I also renamed vat_no to vat_number at the customer.
## Summary by CodeRabbit
* **New Features**
* Added support for a new "tax identifier" field in addresses, orders,
carts, and customer records, including form inputs, table displays, and
PDF invoices.
* Introduced translations for the "tax identifier" field across multiple
languages (English, German, Spanish, French, Dutch, Polish, Vietnamese).
* **Refactor**
* Renamed all occurrences of "VAT No." to "Tax Identifier" in
customer-related fields, forms, and labels.
* Updated searchable data and global search attributes to use "tax
identifier" instead of "vat_no".
* **Documentation**
* Updated documentation and code examples to reference "tax identifier"
instead of "vat_no" and to include the new field where relevant.
* **Tests**
* Adjusted unit tests to use "tax_identifier" in place of "vat_no".
---------
Co-authored-by: Glenn Jacobs
The company's VAT number was not displayed at the order details (nor in
the generated PDF) on backend, and it should if the order was made by a
legal person.
Please check the related issue for more details:
#2070
As you suggested I added a new vat number field to the DB to all the 3
address tables.
I also renamed vat_no to vat_number at the customer.
## Summary by CodeRabbit
* **New Features**
* Added support for a new "tax identifier" field in addresses, orders,
carts, and customer records, including form inputs, table displays, and
PDF invoices.
* Introduced translations for the "tax identifier" field across multiple
languages (English, German, Spanish, French, Dutch, Polish, Vietnamese).
* **Refactor**
* Renamed all occurrences of "VAT No." to "Tax Identifier" in
customer-related fields, forms, and labels.
* Updated searchable data and global search attributes to use "tax
identifier" instead of "vat_no".
* **Documentation**
* Updated documentation and code examples to reference "tax identifier"
instead of "vat_no" and to include the new field where relevant.
* **Tests**
* Adjusted unit tests to use "tax_identifier" in place of "vat_no".
---------
Co-authored-by: Glenn Jacobs
PreviousNext