Why did my update get marked CRITPATH? It doesn't look like I can even set that flag, much less by accident...

Thanks,
Richard
---------- Forwarded message ----------
From: <updates@fedoraproject.org>
Date: Mon, Feb 26, 2018 at 11:33 AM
Subject: [Fedora Update] [CRITPATH] [comment] soxr-0.1.3-1.fc27
To: hobbes1069@gmail.com


The following comment has been added to the soxr-0.1.3-1.fc27 update:

bodhi - 2018-02-26 17:33:34.124156 (karma: 0)
This update has been pushed to testing.

To reply to this comment, please visit the URL at the bottom of this mail

================================================================================
     soxr-0.1.3-1.fc27
================================================================================
  Update ID: FEDORA-2018-63caeb457a
    Release: Fedora 27
     Status: testing
       Type: bugfix
   Severity: low
      Karma: 0
   Critpath: True
    Request: testing
       Bugs: 1548697 - soxr-0.1.3 is available
      Notes: Version 0.1.3 (2018-02-24)    * SIMD enhancements: SSE, AVX, Neon.
           : * Improve support for clang, ARM, and cross-
           : compilation.   * Provide env. var. override of runtime
           : parameters.   * Build fix re cmake variables
           : AVCODEC_INCLUDE_DIRS & AVUTIL_INCLUDE_DIRS.   * Build
           : options WITH_SINGLE_PRECISION, WITH_DOUBLE_PRECISION &
           : WITH_SIMD have     been removed; replacement options
           : are detailed in INSTALL, `Resampling     engines'.
  Submitter: hobbes1069
  Submitted: 2018-02-26 13:29:41.889116
   Comments: bodhi - 2018-02-26 13:29:41.906109 (karma 0)
             This update has been submitted for testing by
             hobbes1069.
             bodhi - 2018-02-26 17:33:34.124156 (karma 0)
             This update has been pushed to testing.

  https://bodhi.fedoraproject.org/updates/FEDORA-2018-63caeb457a