* fix(types): use SeverityLevel

* fix(types): remove other references to the enum

* fix(types): disable deprecation warning

* fix(types): move fromString to utils

* packages(types): fix exports

* fix(rebase): fix conflicts

* ref(types): deprecate status enum (#4298)

* ref(types): deprecate enum and export type

* ref(types): fix fromHttpCode usage to statusFromHttpCode

* ref(types): remove enum usage

* fix(types): fix mistake on span

* fix: fmt

* ref(types): do not export the status enum

* ref(types): fix all imports

* ref(utils): consistent naming

* ref(types): deprecate span status enum (#4299)

* ref(span): deprecate span status enum

* ts(span): widen type

* ref(span): avoid reexporting the enum

* ref(types): fix all imports

* fix(test): remove extra space

* fix(test): import extension methods

* ref(types): deprecate transactionmethod enum (#4314)

* ref(types): deprecate transactionmethod enum

* fix(types): drop transactionsamplingmethod

* ref(types): deprecate outcome enum (#4315)

* ref(types): deprecate outcome enum

* fix(types): drop transportoutcome

* ref(types): deprecate request status enum (#4316)

* ref(types): deprecate request status

* ref(types): deprecate session status

* ref(types): remove unused logLevel (#4317) (#4320)

Co-authored-by: Armin Ronacher <[email protected]>

Co-authored-by: Armin Ronacher <[email protected]>

In #4280,
specifically in commit dd3aa70, we
deprecated the `Severity` enum in favour of using a string union type,
`SeverityLevel`. It's important to note that this change affected the
type signature of one of our public API methods, `captureMessage`.

The change to deprecate the `Severity` enum was done for bundle size
reasons.

After releasing the beta with these changes, it was found that
deprecating the `Severity` enum and replacing it with `SeverityLevel`
was quite the disruptive change, which would make upgrading to the minor
version a hassle for users. As a result, this patch undeprecates the
`Severity` enum. The `Severity` enum will be removed in the upcoming
major release instead, as a breaking change.

In #4280,
specifically in commit dd3aa70, we
deprecated the `Severity` enum in favour of using a string union type,
`SeverityLevel`. It's important to note that this change affected the
type signature of one of our public API methods, `captureMessage`.

The change to deprecate the `Severity` enum was done for bundle size
reasons.

After releasing the beta with these changes, it was found that
deprecating the `Severity` enum and replacing it with `SeverityLevel`
was quite the disruptive change, which would make upgrading to the minor
version a hassle for users. As a result, this patch undeprecates the
`Severity` enum. The `Severity` enum will be removed in the upcoming
major release instead, as a breaking change.

In #4280,
specifically in commit dd3aa70, we
deprecated the `Severity` enum in favour of using a string union type,
`SeverityLevel`. It's important to note that this change affected the
type signature of one of our public API methods, `captureMessage`.

The change to deprecate the `Severity` enum was done for bundle size
reasons.

After releasing the beta with these changes, it was found that
deprecating the `Severity` enum and replacing it with `SeverityLevel`
was quite the disruptive change, which would make upgrading to the minor
version a hassle for users. As a result, this patch undeprecates the
`Severity` enum. The `Severity` enum will be removed in the upcoming
major release instead, as a breaking change.

In #4280,
specifically in commit dd3aa70, we
deprecated the `Severity` enum in favour of using a string union type,
`SeverityLevel`. It's important to note that this change affected the
type signature of one of our public API methods, `captureMessage`.

The change to deprecate the `Severity` enum was done for bundle size
reasons.

After releasing the beta with these changes, it was found that
deprecating the `Severity` enum and replacing it with `SeverityLevel`
was quite the disruptive change, which would make upgrading to the minor
version a hassle for users. As a result, this patch undeprecates the
`Severity` enum. The `Severity` enum will be removed in the upcoming
major release instead, as a breaking change.

In #4280,
specifically in commit dd3aa70, we
deprecated the `Severity` enum in favour of using a string union type,
`SeverityLevel`. It's important to note that this change affected the
type signature of one of our public API methods, `captureMessage`.

The change to deprecate the `Severity` enum was done for bundle size
reasons.

After releasing the beta with these changes, it was found that
deprecating the `Severity` enum and replacing it with `SeverityLevel`
was quite the disruptive change, which would make upgrading to the minor
version a hassle for users. As a result, this patch undeprecates the
`Severity` enum. The `Severity` enum will be removed in the upcoming
major release instead, as a breaking change.