Skip to content

Commit be25e9f

Browse files
committed
chore: bump version to 1.2.1 and update changelog
- Update package.json version to 1.2.1 - Add comprehensive changelog entries for versions 1.2.1, 1.2.0, and 1.1.3 - Document Customer implementation improvements and API alignment fixes - Include security updates and endpoint URL fixes from recent releases
1 parent 4eb9cb3 commit be25e9f

File tree

2 files changed

+58
-1
lines changed

2 files changed

+58
-1
lines changed

CHANGELOG.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,63 @@ All notable changes to this project will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8+
## [1.2.1] - 2025-09-08
9+
10+
### Fixed
11+
12+
- **Customer API Alignment** - Made `description` field required in `CustomerCreateParams` to match API requirements
13+
- **Customer Type Definitions** - Added missing `name` field to Customer interface for better type safety
14+
- **Customer Sources** - Properly typed `sources` field as `Source[]` array with correct import
15+
16+
### Enhanced
17+
18+
- **Customer Name Handling** - Implemented automatic name to metadata mapping for API compatibility while preserving backward compatibility
19+
- **Metadata Preservation** - Enhanced metadata handling to preserve existing metadata when adding name field
20+
- **Response Processing** - Added name extraction from metadata in all Customer response methods (create, retrieve, update, retrieveByEmail)
21+
- **Test Coverage** - Added comprehensive test suite covering name handling edge cases and metadata preservation
22+
23+
### Technical Improvements
24+
25+
- Updated all test cases to include required description field
26+
- Enhanced Customer resource implementation with robust name-to-metadata transformation
27+
- Improved type safety across Customer-related operations
28+
- Maintained full backward compatibility for existing Customer API usage
29+
30+
## [1.2.0] - 2025-09-08
31+
32+
### Added
33+
34+
- **Charge Status Property** - Added `status` property to Charge interface for better charge state tracking
35+
36+
### Fixed
37+
38+
- **Customer API Endpoints** - Resolved customer API endpoint URL issues and improved path handling
39+
- **Customer Tests** - Updated customers test to match correct `retrieveByEmail` endpoint
40+
- **Payment Request Response** - Normalized payment request void response structure for consistency
41+
- **Charge Endpoint URLs** - Fixed endpoint URLs for charge operations
42+
43+
### Removed
44+
45+
- **BREAKING: Charge Verify Functionality** - Removed `verify()` method from ChargesResource for security reasons
46+
- **ChargeVerifyParams Interface** - Removed all charge verification related types and documentation
47+
48+
### Security
49+
50+
- Eliminated charge verification functionality to prevent potential security vulnerabilities
51+
52+
## [1.1.3] - 2025-09-07
53+
54+
### Fixed
55+
56+
- **CheckoutSessions URL Construction** - Fixed Invalid URL error in CheckoutSessions endpoints
57+
- **Base Path Handling** - Resolved URL construction creating double slashes in API endpoints (e.g., `https://api.pay.magpie.im//cs_123`)
58+
- **Sessions Resource** - Updated CheckoutSessions resource to prevent malformed URLs
59+
60+
### Technical Improvements
61+
62+
- Enhanced base resource URL handling to normalize path construction
63+
- Updated session tests to reflect correct URL patterns
64+
865
## [1.1.2] - 2025-09-07
966

1067
### Fixed

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@magpieim/magpie-node",
3-
"version": "1.2.0",
3+
"version": "1.2.1",
44
"description": "The Magpie API Library for NodeJS enables you to work with Magpie APIs.",
55
"keywords": [
66
"magpie",

0 commit comments

Comments
 (0)