NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #2698 by repository stars
Latest stable
v0.26.4
Last release 13 days ago
09 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 46 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
224 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Thank you @svz-ya, for the contributions!
Thank you @svz-ya, for the contributions!
Nothing published for this version
Add EBCDIC 1047 encoder & prefixer #190
Kudos to @Dakinola892 for the contributions!
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Introduce a SafeError type which is used to wrap around external errors, preventing the returned error message from displaying sensitive information,
SafeError type which is used to wrap around external errors, preventing the returned error message from displaying sensitive information, while still allowing errors to be matched (#185)SafeError type to wrap external errors in the field and encoding packages, as these operate on the potentially sensitive data. Errors from prefix and network packages were not changed since these only operate on the length part of the data, exposing their details should be okay. (#185)Kudos to @cheukwing for the contributions!
Return error when packing fields with zero length
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
index tag of the field has priority over the field name when (un)marshal message data using go structs #168
index tag of the field has priority over the field name when (un)marshal message data using go structs #168Nothing published for this version
move describe.Message(out, mesage) into iso8583.Describe(message, out)
describe.Message(out, mesage) into iso8583.Describe(message, out)message.Marshal(data) - it will make it easier to migrate from SetData as similar behavior was supported in it.Nothing published for this version
Nothing published for this version
Nothing published for this version
deprecated message.SetData(data). Use message.Marshal() instead.
message.Marshal(data) which sets values of message fields using values provided in the data struct.index tag for both message.Marshal() and message.Unmarshal(). Now you can name your fields as you want and use index tag to specify the field index matching the ISO8583 specification. Examples are here and here.iso8583.Unmarshal. Please, use message.Unmarshal instead.message.SetData(data). Use message.Marshal() instead.field.SetData(data). Use field.Marshal(data) instead.message.SetData(data). Before it could be used to get values into a struct after calling message.Unpack() like this:data := &ISOMessage{}
mesage.SetData(data)
message.Unpack(rawMessage)
data.F1.Value // in previous versions, values were populated during unpacking, but now they are not
Now message.SetData(data) only sets field values and you can't get values back to the struct using it. In order to get values into the struct you have to use message.Unmarshal(data) like this:
message.Unpack(rawMessage)
data := &ISOMessage{}
mesage.Unmarshall(data)
data.F1.Value // now you can get the value
Two main changes that you may need to do in your code:
message.SetData(data) with message.Marshal(data). Latter simply sets field values with values provided in the data struct. Without any side effects.message.Data()(*YouMessageTypehere) with message.Unmarshal(data). It sets data struct values with message field values. No side-effects.SetData() with Unpack to get access to message field values, then you have to replace it with just message.Unmarshal(data).You have to change your code from this
type ISO87Data struct {
F0 *field.String
F2 *field.String
F4 *field.String
}
message := NewMessage(spec)
data := &ISO87Data{}
err := message.SetData(data) // you "link" data internally
err = message.Unpack(rawMsg) // here values are populated into linked data struct. it will not work anymore.
// access field values
data.F0.Value
data.F2.Value
data.F4.Value
to this:
type ISO87Data struct {
F0 *field.String
F2 *field.String
F4 *field.String
}
message := NewMessage(spec)
err := message.Unpack(rawMsg)
data := &ISO87Data{}
err = message.Unmarshal(data)
// access field values
data.F0.Value
data.F2.Value
data.F4.Value
If you have any questions, please, submit an issue or ask in our community Slack channel.
deprecated message.SetData(data). Use message.Marshal() instead.
Changes in this PR are not backward compatible! Few things have changed. Hopefully, migration will not be painful for you. If you have any questions, please, let us know here or in our community Slack channel.
message.Marshal(data) which sets values of message fields using values provided in data struct.index tag for both message.Marshal() and message.Unmarshal(). Now you can name your fields as you want and used index tag to specify field index in the ISO8583 specification. Examples are here and here.iso8583.Unmarshal. Please, use message.Unmarshal instead.message.SetData(data). Use message.Marshal() instead.field.SetData(data). Use field.Marshal(data) instead.message.SetData(data). Before it could be used to get values into a struct after calling message.Unpack() like this:data := &ISOMessage{}
mesage.SetData(data)
message.Unpack(rawMessage)
data.F1.Value // if previous versions values were populated during unpacking, but now they are not
Now message.SetData(data) only sets field values. No way to get values back to the struct. In order to get values into struct you have to use message.Unmarshal(data) like this:
message.Unpack(rawMessage)
data := &ISOMessage{}
mesage.Unmarshall(data)
data.F1.Value // now you can get the value
Two main changes that you may need to do in your code:
message.SetData(data) with message.Marshal(data). Latter, simply sets field values with values provided in the data struct. Without any side-effects.message.Data()(*YouMessageTypehere) with message.Unmarshal(data). It sets data` struct values with message field values. No side-effects.SetData() and call Unpack to get access to message field values, replace it with message.Unmarshal(data).You have to change your code from this
type ISO87Data struct {
F0 *field.String
F2 *field.String
F4 *field.String
}
message := NewMessage(spec)
data := &ISO87Data{}
err := message.SetData(data) // you "link" data internally
err = message.Unpack(rawMsg) // here values are populated into linked data struct. no more.
// now you access you
data.F0.Value
data.F2.Value
data.F4.Value
to this:
type ISO87Data struct {
F0 *field.String
F2 *field.String
F4 *field.String
}
message := NewMessage(spec)
err := message.Unpack(rawMsg)
data := &ISO87Data{}
err = message.Unmarshal(data)
// now you access fields in data
data.F0.Value
data.F2.Value
data.F4.Value
Nothing published for this version
Nothing published for this version
Deprecated: message.Data() will be removed in the next release. Please, use iso8583.Unmarshal instead (see the example here).
message.Unpack(nil) or empty/smaller than expected input slice length (#161)iso8583.Unmarshal method to populate data struct with message field values (#157)message.Data() will be removed in the next release. Please, use iso8583.Unmarshal instead (see the example here).Nothing published for this version
added a missing rightPadder to JSON spec builder by @adamdecaf in https://github.com/moov-io/iso8583/pull/156
rightPadder to JSON spec builder by @adamdecaf in https://github.com/moov-io/iso8583/pull/156Full Changelog: https://github.com/moov-io/iso8583/compare/v0.8.2...v0.8.4
Nothing published for this version
Nothing published for this version
Extend MTI enum (#153) (add reversal response, administrative messages, network management, etc.)
Fix issue with packing zero length fields #149
Clone() method for iso8583 message #150Nothing published for this version
Replace %v with %w in error messages
Fix BCD decoding to limit number of bytes being read from source #137
Use = as default the separator in Track 2 #135
= as default the separator in Track 2 #135Support 'D' separator in Track 2 #134
This should be regarded to be a breaking change even though the API itself is unchanged.
Various encoding / decoding fixes:
field.JSONUnmarshal methods now unquote values using the json.Unmarshal rather than using strconv.Unquote. This is because the json.Unmarshal function is more robust and handles a wider range of edge cases.field/Binary MarshalJSON and UnmarshalJSON returns hex based strings and takes them in respectively. Previously, they handled bas64 representations of bytes making them pretty unusable in their string formats. This should be regarded to be a breaking change even though the API itself is unchanged.field/Bitmap no longer supports JSON encoding / decoding. The decision was made to do this because bitmaps add little value in JSON form and are used specifically for the parsing of ISO8583 messages with no business use case.field/Composite now lazily creates subfields only if they are being packed or unpacked rather than creating all subfields when defined in the spec regardless of whether they are to be populated with values or not. This change was necessary to ensure that only relevant fields are populated in their JSON format. Before, even unpopulated fields were populated with "" or null values. This caused issues when unmarshalling in that JSON representation back into the iso8583.Message.spec.CreateSubfields with field.CreateSubfield. Due to the change in how Composite now creates fields, we needed to change the function signature of this function.Added Track Data support (track 1, track 2, track 3) https://github.com/moov-io/iso8583/pull/124
Nothing published for this version
IMPROVEMENTS: * #129 Support composite fields in specs.Builder (to export/import iso8583 spec into/from JSON)
IMPROVEMENTS:
specs.Builder (to export/import iso8583 spec into/from JSON)Nothing published for this version
Add JSON Unmarshaler for Message and Fields
IMPROVEMENTS
Nothing published for this version
Nothing published for this version
Add support for configurable subfield sorting for composite fields
IMPROVEMENTS
Nothing published for this version
This version is the same as v0.5.0 but with improved release infrastructure.
This version is the same as v0.5.0 but with improved release infrastructure.
refactor field.Spec and Composite field type to support string tag encoding
BREAKING CHANGES
ADDITIONS
Nothing published for this version
Added VMLH - Visa Message Length Header 067fd46
Added list of constants for MTI parsing of ISO 8583:1987 (constants.go)
spec-file flag to CLI to describe message with any spec (not only hardcoded) described in JSON format:➜ ./bin/iso8583 describe -spec-file ./examples/specs/spec87ascii.json msg.bin
Nothing published for this version
Add: EBCDIC encoding based on https://www.ibm.com/docs/en/iis/11.3?topic=tables-ebcdic-ascii
Add: EBCDIC encoding based on https://www.ibm.com/docs/en/iis/11.3?topic=tables-ebcdic-ascii
Add: field.Binary - to store binary data and display it in Hex encoding
Fix: describe.Message panics when describing message without bitmap
Fix: in field.Composite on Unpack stop parsing bytes once prefix length limit is reached
Fix: add 0 padding to DE3 of specs.Spec87ASCII specification
Nothing published for this version
CLI describe will try to describe the message even if some fields fail to unpack
./specsName field which is useful for debuggingNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
a78e8cd Merge pull request #87 from moov-io/json-serialize-only-set-fields dfca82a fix CLI installation instructions in README 2b1fef0 serialize into
a78e8cd Merge pull request #87 from moov-io/json-serialize-only-set-fields dfca82a fix CLI installation instructions in README 2b1fef0 serialize into JSON only fileds that were set fa32d43 update Installation instructions
FIXES:
Nothing published for this version
Nothing published for this version
for each release, we generate binary file for CLI for Windows, Linux and Mac
IMPROVEMENTS:
One column per quarter.