Repository navigation
Releases: logqlio/logql-apollo-plugin
Releases · logqlio/logql-apollo-plugin
Release list
0.7.0
Release Notes — v0.7.0
Breaking Changes
LogqlApolloPlugin.fromEnv()is now required to load config from environment variables. Previously the plugin would implicitly merge environment variables with options passed toLogqlApolloPlugin(). Now the two are explicit: pass an options object toLogqlApolloPlugin({ ... }), or callLogqlApolloPlugin.fromEnv()to load entirely from env vars. (#59)
New Features
- User ID collection — The plugin now supports a
userIdoption: a function that receives the request context and headers and returns a user identifier. This is sent alongside error reports to help correlate errors with specific users. (#72) - GraphQL client header support — The plugin now reads both
graphql-client-name/graphql-client-versionheaders (in addition to the existingapollographql-client-*headers) to identify the calling client. (#67) - TypeScript type definitions — Type definitions are now included in the package. (#77)
Internal
- Added CONTRIBUTING.md (#75)
- Switched to provenance-based publishing with OIDC for improved supply chain security (#74)
- Migrated to ESLint 9 (#60)
- Added test coverage for LRU cache behaviour (#68)
- Various dependency security bumps (
qs,form-data,sha.js,formidable,cross-spawn,micromatch,express,braces)
0.6.0
0.5.0
Main changes:
- Use fetch timeout instead of abort controller (allow support for earlier versions of nodes)
- Handle persisted query not found
- Do not send query source when already synced
- Stop logging when verbose mode is off
Other:
- Update dependencies
- Improve test performances
0.4.0
0.3.1
0.3.0
0.2.2
fix: Automatically disable plugin in tests (checking NODE_ENV === 'test' unless option runInTests is set to true.
fix: More resilience of the plugin when invalid envs are passed, they are simply ignored and a warning is emitted
feat: Log errors on launch when invalid config is passed instead of throwing