What's Changed

• fix iss claims for eseye 3.0 by @recursivetree in https://github.com/eveseat/eseye/pull/95

New Contributors

• @Crypta-Eve made their first contribution in https://github.com/eveseat/eseye/pull/96

Full Changelog: https://github.com/eveseat/eseye/compare/3.0.0...3.0.1

What's Changed

• Cleanup request data should be called on successful cache load, also. by @aubreyshomo in https://github.com/eveseat/eseye/pull/77
• Apply fixes from StyleCI by @leonjza in https://github.com/eveseat/eseye/pull/78
• Apply fixes from StyleCI by @leonjza in https://github.com/eveseat/eseye/pull/79
• fix: add missing public route to avoid log spamming by @Rakdos8 in https://github.com/eveseat/eseye/pull/83
• RedisCache: Add missing TTL from expiration date given from ESI by @Rakdos8 in https://github.com/eveseat/eseye/pull/84
• Fix: Rare issue where the expiration timestamp is before now() by @Rakdos8 in https://github.com/eveseat/eseye/pull/85
• Apply fixes from StyleCI by @warlof in https://github.com/eveseat/eseye/pull/86
• Fix: Error handling in case of return code 502 by @Rakdos8 in https://github.com/eveseat/eseye/pull/88
• fix iss claim by @recursivetree in https://github.com/eveseat/eseye/pull/94

New Contributors

• @aubreyshomo made their first contribution in https://github.com/eveseat/eseye/pull/77
• @Rakdos8 made their first contribution in https://github.com/eveseat/eseye/pull/83
• @recursivetree made their first contribution in https://github.com/eveseat/eseye/pull/94

Full Changelog: https://github.com/eveseat/eseye/compare/2.4.0...2.4.1

What's New

• Sample tool has been updated to use JWT tokens
• Eseye is non longer strongly coupled to Guzzle Http client and can be connected to any library PSR-17 and PSR-18 compliants
• Eseye is now PSR-16 compliant and can be natively used with Laravel Cache engine
• Eseye is now PSR-3 compliant and can be natively used with Laravel Log Engine

What's Changed

• Cleanup request data should be called on successful cache load, also. by @aubreyshomo in https://github.com/eveseat/eseye/pull/77
• refactor: reduce coupling and bump to php 8 by @warlof in https://github.com/eveseat/eseye/pull/81
• Refactor cache handler by @warlof in https://github.com/eveseat/eseye/pull/80
• JWT management has been outsourced from Fetcher by @warlof in https://github.com/eveseat/eseye/commit/4468d4a35226e287144bedcd922a7444c8a213bd
• ESI Response are now always attached to log when used with Debug level by @warlof in https://github.com/eveseat/eseye/commit/f41f66f1943026ca38807063d67fa2a342b5e60e
• Eseye is now meeting Cache-Control HTTP header and will non longer store response with either no-cache or no-store value by @warlof in https://github.com/eveseat/eseye/commit/11b5998825204a7fa12864cda55e08091b55f310
• EsiResponse API has been altered and getHeader method is now returning an array of value matching the requested HTTP header. For conveniency, method getHeaderLine has been introduced, reproducing previous ability
• Due to dependency decoupling, fetcher class has been moved from \Seat\Eseye\Fetchers\GuzzleFetcher to \Seat\Eseye\Fetchers\Fetcher
• PHP minimum supported version is now 8.1

New Contributors

• @aubreyshomo made their first contribution in https://github.com/eveseat/eseye/pull/77

Full Changelog: https://github.com/eveseat/eseye/compare/2.4.0...3.0.0

Enhancement

• Eseye can now use either Guzzle 6 or Guzzle 7 (eveseat/eseye#67, eveseat/eseye#73)

Fix

• add /alliances/{alliance_id}/contacts/labels/ endpoint to granted list

Fix

• grant /characters/{character_id}/orders/history/ endpoint
• grant /corporations/{corporation_id}/orders/history/ endpoint

Feat

• give ability to determine if an instance is authenticated or not

Ship the library with an updated toolbox to retrieve JWT Tokens / using OAuth v2 endpoints

This version address an issue with cache system and EsiResponse container serialization.

Previous versions were not building proper serialized object when response was containing an array. As a result, cached response was not usable and Eseye need to sent a new request even if content didn't expires.

Cache based on ETag response have been improved aswel to update internal content instead sending requests continuously.

Be sure you are clearing cache after this update as existing content will non longer be valid.