# Change Log

## vNEXT

- _Nothing yet! Stay tuned!_

## 0.6.0

- __BREAKING__: Drop support for checking for "legacy" manifest locations.  These legacy manifests were deprecated when `v0.2.0` of the operation registry plugin was released.  In order to provide support for both manifests, the plugin has continued to poll for legacy operation manifests in the event that the new format could not be located.  With this change, this legacy probing will cease.  **We will continue to host the legacy manifests until September 30, 2020.**  Users are encouraged to update to this version to ensure that they are not inadvertently leveraging legacy manifests any longer. [PR #4330](https://github.com/apollographql/apollo-server/pull/4330)
- __BREAKING__: Drop use of `loglevel-debug`.  This removes the very long date and time prefix in front of each log line and also the support for the `DEBUG=apollo-server:apollo-server-plugin-operation-registry:*` environment variable.  Both of these were uncommonly necessary or seldom used (with the environment variable also being undocumented).  The existing behavior can be preserved by providing a `logger` that uses [`loglevel-debug`](https://npm.im/loglevel-debug), if desired.  [PR #4327](https://github.com/apollographql/apollo-server/pull/4327)
- __BREAKING__: Drop support for `schemaTag` with `graphVariant` being its successor.  As noted below, `schemaTag` was deprecated in v0.3.1 and a deprecation warning has been shown since.  The `graphVariant` replaces the functionality that `schemaTag` offered and, aside from the name change, its behavior is identical. [PR #4328](https://github.com/apollographql/apollo-server/pull/4328)

## 0.4.4

- Reinstate typings for `make-fetch-happen` at the `apollo-gateway` project level (and now, additionally, `apollo-server-plugin-operation-registry`) [PR #4333](https://github.com/apollographql/apollo-server/pull/4333)

## 0.4.3

- Switch from using our own HTTP _retries_ and _conditional-request_ implementation built on top of [`node-fetch`](https://npm.im/node-fetch) to a third-party "Fetcher" (i.e., a [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)-compliant implementation) called [`make-fetch-happen`](https://npm.im/make-fetch-happen). [PR #TODO]()

## 0.4.2

- Only changes in dependencies.

## 0.4.1

- __BREAKING__: Use a content delivery network, fetch storage secrets and operation manifests from different domains: https://storage-secrets.api.apollographql.com and https://operations.api.apollographql.com. Please mind any firewall for outgoing traffic.

## 0.4.0:

- This version was accidentally skipped due to a manual update of `package.json`, see `v0.4.1` - @trevor-scheer

## 0.3.1:

- The `schemaTag` option is now deprecated and superseded by `graphVariant`.

## 0.3.0

- Add lifecycle hooks: `onUnregisteredOperation`, and `onForbiddenOperation`.
- Prevent the polling timer from keeping the event loop active
- Update error message for operations that are not in the operation registry.

## 0.2.2

- Update `README` image.

## 0.2.1

- Don't enable logging if `debug` was explicitly set to `false` even if `dryRun` is set to `true`.

## 0.2.0

- Per-tag operation manifests can now be fetched for each tag that has a schema and registered operations.
- Manifest storage path structure updated to `/${graphId}/${storageSecret}/${graphVariant}/manifest.v2.json`. The storage secret is fetched automatically using your API key. No longer uses schema hash.
- Metrics on forbidden and registered operations are now reported to Engine

## 0.1.0

- `apollo-server-plugin-operation-registry`
- Update operation registry plugin to use manifest v2