Remove old "introduced in" notices

docs/models/dcim/devicerole.md

@@ -6,8 +6,6 @@ Devices can be organized by functional roles, which are fully customizable by th
 
 ### Parent
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The parent role of which this role is a child (optional).
 
 ### Name

docs/models/dcim/interface.md

@@ -126,8 +126,6 @@ The tagged VLANs which are configured to be carried by this interface. Valid onl
 
 ### Q-in-Q SVLAN
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The assigned service VLAN (for Q-in-Q/802.1ad interfaces).
 
 ### Wireless Role
@@ -155,6 +153,4 @@ The [wireless LANs](../wireless/wirelesslan.md) for which this interface carries
 
 ### VLAN Translation Policy
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The [VLAN translation policy](../ipam/vlantranslationpolicy.md) that applies to this interface (optional).

docs/models/dcim/inventoryitem.md

@@ -30,8 +30,6 @@ An alternative physical label identifying the inventory item.
 
 ### Status
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The inventory item's operational status.
 
 ### Role

docs/models/dcim/macaddress.md

@@ -1,7 +1,5 @@
 # MAC Addresses
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 A MAC address object in NetBox comprises a single Ethernet link layer address, and represents a MAC address as reported by or assigned to a network interface. MAC addresses can be assigned to [device](../dcim/device.md) and [virtual machine](../virtualization/virtualmachine.md) interfaces. A MAC address can be specified as the primary MAC address for a given device or VM interface.
 
 Most interfaces have only a single MAC address, hard-coded at the factory. However, on some devices (particularly virtual interfaces) it is possible to assign additional MAC addresses or change existing ones. For this reason NetBox allows multiple MACAddress objects to be assigned to a single interface.

docs/models/dcim/moduletypeprofile.md

@@ -1,7 +1,5 @@
 # Module Type Profiles
 
-!!! info "This model was introduced in NetBox v4.3."
-
 Each [module type](./moduletype.md) may optionally be assigned a profile according to its classification. A profile can extend module types with user-configured attributes. For example, you might want to specify the input current and voltage of a power supply, or the clock speed and number of cores for a processor.
 
 Module type attributes are managed via the configuration of a [JSON schema](https://json-schema.org/) on the profile. For example, the following schema introduces three module type attributes, two of which are designated as required attributes.

docs/models/dcim/poweroutlet.md

@@ -40,12 +40,8 @@ The operational status of the power outlet. By default, the following statuses a
 !!! tip "Custom power outlet statuses"
     Additional power outlet statuses may be defined by setting `PowerOutlet.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.
 
-!!! info "This field was introduced in NetBox v4.3."
-
 ### Color
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The power outlet's color (optional).
 
 ### Power Port

docs/models/dcim/racktype.md

@@ -42,8 +42,6 @@ The number of the numerically lowest unit in the rack. This value defaults to on
 
 The external width, height and depth of the rack can be tracked to aid in floorplan calculations. These measurements must be designated in either millimeters or inches.
 
-!!! info "The `outer_height` field was introduced in NetBox v4.3."
-
 ### Mounting Depth
 
 The maximum depth of a mounted device that the rack can accommodate, in millimeters. For four-post frames or cabinets, this is the horizontal distance between the front and rear vertical rails. (Note that this measurement does _not_ include space between the rails and the cabinet doors.)