PublicApi.ForumThreads.Report(string subject, string body, ForumThreadsReportOptions options)
No longer functions, always returns null. Reporting abuse by creating a new thread in the Reporting forum is no longer supported. Reporting abuse is now done through the Abuse service. Method is set to Obsolete but will not fail on compilation. This could be considered a breaking change.
LISTing REST and in-process API Activity Messages
Still have same parameters and return similarly formatted content but the results are not exactly the same as previous versions. Recommend using the Activity Stories endpoints and methods instead. This is a non-breaking change.
Comment IDs will change
Because of the consolidation of all comments with the Comment Service and the migration from app specific tables to a common tables, the unique identifiers for comments will change between version 6.x and 7.0. This is not a concern with the site itself because we did not have permalinks or anything using the unique identifiers. However, if customers were storing those integer ID, then they should be aware that they are changing and make necessary adjustments. This is a non-breaking change for most customers and partners.
- Existing Custom Search Providers will not work
Because of the changes to Search, any existing custom search providers will not work and will need to be rewritten. Search providers were not a Public API or recommended extension point in previous versions, but they were supported. While it is not necessarily a breaking Public API change, customers and partners especially should be aware of these changes.